The PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes WordPress plugin before
Source GCVE Database
Not known to be exploited : upgrade to 4.3.1 soon.
Data as of 6 Nov 2026, 07:20 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 4.3.1
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes (WordPress plugin) to 4.3.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes | Affected
| Fixed in
|
AI-suggested
The vulnerability is fixed in PublishPress Revisions version 4.3.1. Users should upgrade to version 4.3.1 or later to remediate this issue. No other mitigation or workaround information is provided.
Description
The PublishPress Revisions WordPress plugin before version 4.3.1 contains an access control vulnerability. It fails to verify that a user requesting to duplicate or revise a post actually has access to that specific post, only checking if they can edit posts of that type. This allows users with contributor-level access and above to duplicate private, draft, pending, or scheduled posts owned by other users and read their full content.