CVE-2026-114696

Page and Post Restriction <= 1.6.0 - Missing Authorization

2026-10-22 08:46
souparna majumder

Strategic Overview

Status
Patched in 1.6.1
Affected Version
<= 1.6.0
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-114696
View all Page and Post Restriction vulnerabilities

At a glance

CVE-2026-114696 is a medium-severity Missing Authorization vulnerability in the Page and Post Restriction WordPress plugin, affecting versions <= 1.6.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.6.1; sites on affected versions should update now. Disclosed October 2026, reported by souparna majumder.

Vulnerability Overview

The Page and Post Restriction plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 1.6.0. This is due to a missing capability check on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Page and Post Restriction <= 1.6.0 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Page and Post Restriction the fix is 1.6.1: builds <= 1.6.0 are affected, anything from 1.6.1 onward is not.

Remediation

Update to version 1.6.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Page and Post Restriction 1.6.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C