Skip to main content
CVE-2026-123086VulnerabilityPublished

The PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes plugin for WordPress is

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-123086· High 8.1

Not known to be exploited · CVSS 8.1 High.

Data as of 21 Nov 2026, 11:12 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.18.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
publishpressPublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content ChangesAffected
  • <=4.3.4
Fixed in–

AI-suggested

Users should monitor the vendor's advisory for updates and apply any forthcoming patches promptly. Until a fix is available, restrict contributor-level access where possible and consider disabling or replacing the PublishPress Revisions plugin to prevent exploitation.

Description

The PublishPress Revisions plugin for WordPress up to version 4.3.4 contains an authorization bypass vulnerability. This flaw allows authenticated users with contributor-level access or higher to permanently delete trashed posts, pages, and revisions owned by any user, including those with higher privileges. The vulnerability arises because the plugin does not properly verify user authorization before allowing deletion actions. Attackers can trivially obtain the required nonce from a static action emitted in a redirect header before WordPress enforces capability checks.

References

Community reviews

Loading reviews…