PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 3.7.22 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 3.7.23
- Affected Plugin
- PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes
- Affected Version
<= 3.7.22- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-25322
At a glance
CVE-2026-25322 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the PublishPress Revisions WordPress plugin, affecting versions <= 3.7.22. 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 3.7.23; sites on affected versions should update now. Disclosed January 2026, reported by lilmingwa13.
Vulnerability Overview
The PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.7.22. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action 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 Revisions <= 3.7.22 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 Revisions the fix is 3.7.23: builds <= 3.7.22 are affected, anything from 3.7.23 onward is not.
Remediation
Update to version 3.7.23, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to PublishPress Revisions: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: PublishPress Revisions 3.7.23 closes this, and updating the plugin is the step that ends it.
- Firewall
- 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