Answer in brief
CVE-2026-123086 records a High severity (CVSS 8.1) vulnerability in PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 4.3.4 - Missing Authorization to Authenticated (Contributor+) Arbitrary Post Deletion via 'pp_revisions_deleted' Parameter. The current sources do not mark it as known exploited. The current feed maps publishpress/PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps publishpress/PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| publishpress/PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changesgeneric | >=0 <=4.3.4 | Not reported |
Published upstream
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 21, 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.
Quoted source text, attributed separately from HOL analysis.