HomeWordPress vulnerabilitiesPublishPress Revisions
PublishPress Revisions vulnerabilities
PublishPress Revisions has 8 known vulnerabilities in this database. The most recent published record is dated 21 Nov 2026.
- Known vulnerabilities
- 8
- Active installs
- 10,000+
- Latest version
- 4.3.2
- Last updated
- 3 Nov 2026
- Most recent
- 21 Nov 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-123086 | High 8.1 | Up to 4.3.4 | No fixed version yet | 1 d ago |
| Broken access control CVE-2026-131730 | Medium 4.3 | Up to 4.3.3 | No fixed version yet | 2 d ago |
| Broken access control CVE-2026-120851 | Medium 4.3 | Up to 4.2.0 | Fixed in a later version (latest 4.3.2) | 6 Nov 2026 |
| Broken access control CVE-2026-118186 | Medium 4.9 | Before 4.3.1 | Fixed in 4.3.1 | 6 Nov 2026 |
| Broken access control CVE-2026-118187 | Low 2.7 | Before 4.3.1 | Fixed in 4.3.1 | 6 Nov 2026 |
| Sensitive data exposure CVE-2026-118188 | Medium 4.3 | Before 4.3.1 | Fixed in 4.3.1 | 6 Nov 2026 |
| Sensitive data exposure CVE-2024-11154 | Medium 4.3 | Up to 3.5.15 | Fixed in a later version (latest 4.3.2) | 20 Nov 2024 |
| Cross-site scripting (XSS) CVE-2024-9436 | Medium 6.1 | Up to 3.5.14 | Fixed in a later version (latest 4.3.2) | 11 Oct 2024 |
Read the published descriptions
- CVE-2026-123086, 21 Nov 2026
- The PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.3.4 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to permanently force-delete arbitrary trashed posts, pages, and revisions owned by any user, including higher-privileged users. The required nonce is trivially harvested by any Contributor-level user because the static 'revisions-deleted' nonce action is emitted in a redirect header on the init hook before WordPress enforces edit.php's capability check, and once obtained it authorizes deletion of any trashed post or revision on the site. CVE record
- CVE-2026-131730, 20 Nov 2026
- Missing Authorization vulnerability in PublishPress PublishPress Revisions revisionary allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects PublishPress Revisions: from n/a through 4.3.3. CVE record
- CVE-2026-120851, 6 Nov 2026
- Missing Authorization vulnerability in PublishPress PublishPress Revisions revisionary allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects PublishPress Revisions: from n/a through 4.2.0. CVE record
- CVE-2026-118186, 6 Nov 2026
- The PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes WordPress plugin before 4.3.1 does not correctly restrict who may publish content, allowing users such as Contributors who can edit but not publish to make unreviewed posts and pages publicly live, bypassing the intended editorial approval workflow. CVE record
- CVE-2026-118187, 6 Nov 2026
- The PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes WordPress plugin before 4.3.1 does not verify that a user requesting to duplicate or revise a post has access to that specific post, only that they can edit posts of that type, allowing users with contributor-level access and above to duplicate another user's private, draft, pending or scheduled post into one they own and read its full content. CVE record
- CVE-2026-118188, 6 Nov 2026
- The PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes WordPress plugin before 4.3.1 does not verify that a user is permitted to read a given post before returning its content through its revision-comparison feature, allowing any authenticated user, including a Subscriber, to read the title, content and excerpt of any other user's private, draft, pending, scheduled or trashed post. CVE record
- CVE-2024-11154, 20 Nov 2024
- 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. CVE record
- CVE-2024-9436, 11 Oct 2024
- The PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the URL in all versions up to, and including, 3.5.14. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. CVE record
What to do if you run PublishPress Revisions
If you run PublishPress Revisions, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new PublishPress Revisions vulnerabilities
Free. We email you when a new vulnerability is published for PublishPress Revisions, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.