CVE-2022-1027

Page Restriction WordPress <= 1.2.6 - Admin+ Stored Cross-Site Scripting

2022-04-09 00:00
Niraj Mahajan

Strategic Overview

Status
Patched in 1.2.7
Affected Version
<= 1.2.6
CVSS
5.5Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-1027
View all Page and Post Restriction vulnerabilities

At a glance

CVE-2022-1027 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Page and Post Restriction WordPress plugin, affecting versions <= 1.2.6. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). The issue is fixed in version 1.2.7; sites on affected versions should update now. Disclosed April 2022, reported by Niraj Mahajan.

Vulnerability Overview

The Page Restriction WordPress (WP) WordPress plugin before 1.2.7 allows bad actors with administrator privileges to the settings page to inject Javascript code to its settings leading to stored Cross-Site Scripting that will only affect administrator users.

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 interaction from a victim user.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in Page and Post Restriction <= 1.2.6 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Page and Post Restriction the fix is 1.2.7: builds <= 1.2.6 are affected, anything from 1.2.7 onward is not.

Remediation

Update to version 1.2.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Page and Post Restriction: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Page and Post Restriction 1.2.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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