PublishPress Revisions 3.6.0 - 4.2.0 - Contributor+ Unapproved Content Publishing via Revision Workflow
- Exploited
- No known exploitation
- Fix
- Fixed in 4.3.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.3.1.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.15% · 4th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 8/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The PublishPress Revisions WordPress plugin, which handles content submission and approval workflows, does not properly restrict who can publish content. A low-privilege user such as a Contributor, who can edit but not publish, can make unreviewed posts and pages publicly live, bypassing the editorial approval process.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.9/10CVSS 4.9
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.3.1.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Unknown PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes
From 3.6.0 · fixed in 4.3.1
Evidence 1
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-118186
Is CVE-2026-118186 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-118186?
PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes: from 3.6.0 before 4.3.1.Source: cve.now feed data
How do I fix CVE-2026-118186?
Upgrade to a fixed version: 4.3.1.Source: cve.now feed data