CVE-2026-118186VulnerabilityPublished 6 Nov 2026

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

Source GCVE Database

Compare

Authoritative record:CVE-2026-118186· High

Not known to be exploited : upgrade to 4.3.1 soon.

Data as of 6 Nov 2026, 07:32 UTC

Severity

High

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-87h6-gmv4-qqpq

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 >=3.6.0 <4.3.1	Fixed in 4.3.1

AI-suggested

Upgrade the PublishPress Revisions plugin to version 4.3.1 or later, where this access control issue has been fixed. No other mitigation is indicated by the available data.

Description

A vulnerability in the PublishPress Revisions WordPress plugin before version 4.3.1 allows users with Contributor-level permissions, who normally cannot publish content, to bypass the editorial approval process and publish posts or pages directly. This flaw undermines the intended content review workflow.

Impact

This vulnerability allows lower-privileged users (Contributors) to publish content without review, potentially leading to unauthorized or inappropriate content being made publicly available on the affected WordPress site. This could impact content integrity and editorial control.

Summary

The PublishPress Revisions plugin for WordPress versions prior to 4.3.1 contains an access control vulnerability that fails to properly restrict publishing capabilities. Users with Contributor roles, who should only be able to edit content but not publish it, can exploit this flaw to make unreviewed posts and pages publicly live, bypassing the editorial approval workflow designed to prevent unauthorized publication.

References

Community reviews

Loading reviews…