{"id":"CVE-2026-118194","kind":"vulnerability","aliases":["CVE-2026-118194"],"related":[],"title":"WordPress Page and Post Restriction plugin: logged-in users' private content readable by visiting sites","description":"The Page and Post Restriction plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.6.1 This is due to the `papr_restrict_page_post_rest_api()` function, hooked on `rest_pre_dispatch`, re-authenticating the current user from the `wordpress_logged_in` cookie via `wp_set_current_user()` for any GET or HEAD REST request where the current user is 0, without verifying a REST nonce — silently undoing the nonce-zeroing that WordPress core's `rest_cookie_check_errors()` performs on cookie-authenticated requests that lack an `X-WP-Nonce` header or `_wpnonce` parameter. Combined with WordPress's permissive REST CORS behavior — which echoes the request `Origin` and sets `Access-Control-Allow-Credentials: true` — this allows an unauthenticated attacker to read REST API GET responses as a logged-in victim, exposing role-restricted and private post/page content, victim user profile data via `/wp-json/wp/v2/users/me`, and comments the victim is authorized to see. This requires the attacker to lure a logged-in user into visiting an attacker-controlled page that issues credentialed cross-origin `fetch` requests against the target site's REST API; no nonce or further victim interaction beyond the page visit is needed.","summary":"The Page and Post Restriction plugin up to and including 1.6.1 re-authenticates visitors from their WordPress login cookie on REST API read requests without checking a nonce. A malicious page visited by a logged-in user can use that cookie to read restricted posts, pages, comments and the user's profile.","severity":"medium","cvss":6.5,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["package","page-and-post-restriction","self-hosted","wordpress","wordpress-plugin"],"not_affected_if":["plugin-not-installed"],"how_to_check":"- Check whether the Page and Post Restriction plugin is installed and at which version (`wp plugin list` or the Plugins screen in wp-admin)\n- Confirm the installed version is `1.6.1` or lower","fix":"- Page and Post Restriction plugin: the sources do not state a fixed version; the vulnerable range is all versions up to and including `1.6.1`","status":"open","published_at":"2026-10-30T06:16:47+00:00","first_seen_at":"2026-10-30T06:28:39+00:00","triaged_at":"2026-10-30T06:29:53+00:00","updated_at":"2026-10-30T06:29:53+00:00","category":"package","confidence":0.7,"triage":{"at":"2026-10-30T06:29:53Z","model":"claude-haiku-5-5","output":{"fix":"- Page and Post Restriction plugin: the sources do not state a fixed version; the vulnerable range is all versions up to and including `1.6.1`","reach":"internet","title":"WordPress Page and Post Restriction plugin: logged-in users' private content readable by visiting sites","impact":"medium","summary":"The Page and Post Restriction plugin up to and including 1.6.1 re-authenticates visitors from their WordPress login cookie on REST API read requests without checking a nonce. A malicious page visited by a logged-in user can use that cookie to read restricted posts, pages, comments and the user's profile.","audience":"businesses","category":"package","nicknames":[],"who_cares":["wordpress","wordpress-plugin","page-and-post-restriction","self-hosted"],"confidence":0.7,"fix_status":"unknown","needs_auth":"unknown","worst_case":"Attacker reads restricted posts and victim profile data via victim's browser","analyst_note":"Check the NVD entry or the plugin's changelog for a fixed version beyond 1.6.1, since the sources do not state one.","how_to_check":"- Check whether the Page and Post Restriction plugin is installed and at which version (`wp plugin list` or the Plugins screen in wp-admin)\n- Confirm the installed version is `1.6.1` or lower\n- unknown whether the sources define a specific configuration that makes it exposed beyond the vulnerable version range","plain_action":"","needs_analyst":true,"not_affected_if":["plugin-not-installed"],"who_is_affected":"Sites running the Page and Post Restriction plugin at version 1.6.1 or lower are exposed, since the flaw lives in its REST API hook. A logged-in editor or member who visits an attacker's page is the victim, so sites where people with access to restricted content browse the web while logged in are the main concern. The sources do not describe a configuration that avoids the flaw in the vulnerable range.","user_interaction":"yes","needs_special_setup":"no","severity_if_unknown":"unknown"},"cost_usd":0.000799,"input_tokens":4484,"output_tokens":701,"severity_before":"medium"},"analyst_status":null,"analyst_note":null,"search":"'-118194':19A,22A '-2026':18A,21A '/wp-json/wp/v2/users/me':245C '0':157C '1.6.1':46B,110C 'access':210C 'access-control-allow-credenti':209C 'allow':212C,216C 'api':58B,121C,223C,286C 'attack':219C,257C,269C 'attacker-control':268C 'authent':49B,101C,130C,181C 'author':251C 'behavior':201C 'beyond':293C 'bypass':102C 'check':62B,175C 'combin':194C 'comment':84B,247C 'content':12A,239C 'control':211C,270C 'cooki':55B,78B,139C,174C,180C 'cookie-authent':179C 'cor':200C 'core':171C 'credenti':213C,274C 'cross':276C 'cross-origin':275C 'current':132C,143C,154C 'cve':17A,20A 'data':243C 'dispatch':127C 'due':113C 'echo':203C 'error':176C 'expos':232C 'fetch':278C 'function':122C 'get':147C,224C 'head':149C 'header':190C 'hook':123C 'host':31B 'includ':45B,109C 'interact':292C 'issu':273C 'lack':184C 'log':8A,72B,137C,229C,262C 'logged-in':7A,71B,228C,261C 'login':54B 'lure':259C 'malici':66B 'need':298C 'nonc':64B,162C,167C,189C,288C 'nonce-zero':166C 'origin':206C,277C 'packag':23B 'page':2A,25B,37B,67B,83B,91C,118C,271C,295C 'page-and-post-restrict':24B 'papr':116C 'paramet':193C 'perform':177C 'permiss':198C 'plugin':6A,35B,41B,95C 'post':4A,27B,39B,82B,93C,119C 'post/page':238C 'pre':126C 'privat':11A,237C 'profil':89B,242C 're':48B,129C 're-authent':47B,128C 'read':59B,80B,221C 'readabl':13A 'request':60B,151C,182C,205C,279C 'requir':255C 'respons':225C 'rest':57B,120C,125C,150C,161C,173C,199C,222C,285C 'restrict':5A,28B,40B,81B,94C,117C,235C 'role':234C 'role-restrict':233C 'see':253C 'self':30B 'self-host':29B 'set':142C,208C 'silent':163C 'site':16A,283C 'target':282C 'true':214C 'unauthent':218C 'undo':164C 'use':76B 'user':10A,74B,87B,133C,144C,155C,241C,264C 'verifi':159C 'version':105C 'via':140C,244C 'victim':231C,240C,249C,291C 'visit':15A,68B,266C,296C 'visitor':50B 'vulner':99C 'without':61B,158C 'wordpress':1A,32B,34B,53B,97C,136C,170C,196C 'wordpress-plugin':33B 'wp':141C,188C 'wpnonc':192C 'x':187C 'x-wp-nonc':186C 'zero':168C","nicknames":[],"mitigations":[],"who_affected":"Sites running the Page and Post Restriction plugin at version 1.6.1 or lower are exposed, since the flaw lives in its REST API hook. A logged-in editor or member who visits an attacker's page is the victim, so sites where people with access to restricted content browse the web while logged in are the main concern. The sources do not describe a configuration that avoids the flaw in the vulnerable range.","tier":"C","verified":{},"analyst_revisit_at":null,"fix_status":"unknown","audience":"businesses","plain_action":null,"first_public_at":"2026-10-30T06:16:47+00:00","kev":null,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","cvss_by":"security@wordfence.com","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-118194","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-118194","severity":null,"published_at":"2026-10-30T06:16:47+00:00","modified_at":"2026-10-30T06:16:47+00:00","first_seen_at":"2026-10-30T06:28:39+00:00","fetched_at":"2026-10-30T06:28:39+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}