PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 3.5.15 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure
Strategic Overview
- Status
- Patched in 3.5.16
- Affected Plugin
- PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes
- Affected Version
<= 3.5.15- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-11154
At a glance
CVE-2024-11154 is a medium-severity Missing Authorization vulnerability in the PublishPress Revisions WordPress plugin, affecting versions <= 3.5.15. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.5.16; sites on affected versions should update now. Disclosed November 2024, reported by Dominik Dziura (Domons).
Vulnerability Overview
The PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.5.15 via the 'actAjaxRevisionDiffs' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract sensitive data including revisions of posts and pages.
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-862: Missing Authorization
PublishPress Revisions <= 3.5.15 carries this weakness at actAjaxRevisionDiffs, and reaching it takes an account at Subscriber level or above. 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 PublishPress Revisions the fix is 3.5.16: builds <= 3.5.15 are affected, anything from 3.5.16 onward is not.
Remediation
Update to version 3.5.16, 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: PublishPress Revisions 3.5.16 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C