PublishPress Capabilities: User Role Access Control, Admin Area Permissions <= 2.50.1 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.51.0
- Affected Version
<= 2.50.1- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-94487
At a glance
CVE-2026-94487 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the PublishPress Capabilities WordPress plugin, affecting versions <= 2.50.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.51.0; sites on affected versions should update now. Disclosed September 2026, reported by Intrudify.
Vulnerability Overview
The PublishPress Capabilities: User Role Access Control, Admin Area Permissions plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.50.1. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in PublishPress Capabilities <= 2.50.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For PublishPress Capabilities the fix is 2.51.0: builds <= 2.50.1 are affected, anything from 2.51.0 onward is not.
Remediation
Update to version 2.51.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to PublishPress Capabilities: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: PublishPress Capabilities 2.51.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in PublishPress Capabilities: User Role Access Control, Admin Area Permissions
- 9.8CVE-2021-25032: PublishPress Capabilities Arbitrary Options Update
CVE-2021-25032 - 7.2CVE-2026-75927: PublishPress Capabilities Privilege Escalation
CVE-2026-75927 - 7.2CVE-2022-3366: PublishPress Capabilities <= 2.5.1 PHP Object Injection
CVE-2022-3366 - 7.2PublishPress Capabilities <= 1.5.8 SQL Injection
- 6.1PublishPress Capabilities <= 2.3.2 Reflected Cross-Site Scripting
- 4.7CVE-2026-28183: PublishPress Capabilities Privilege Escalation
CVE-2026-28183 - 4.7CVE-2026-48197: PublishPress Capabilities Privilege Escalation
CVE-2026-48197 - 4.3CVE-2026-32394: PublishPress Capabilities Missing Authorization
CVE-2026-32394
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C