PublishPress Revisions 3.9.0 - 4.2.0 - Subscriber+ Unpublished Content Disclosure
- 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.14% · 3rd 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? →
- 7/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, a tool for submitting, approving, and scheduling content changes, has a flaw in its revision-comparison feature. Any logged-in user, including one with only Subscriber access, can read the title, content, and excerpt of other users' private, draft, pending, scheduled, or trashed posts.
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 verify that a user is permitted to read a given post before returning its content through its revision-comparison feature, allowing any authenticated user, including a Subscriber, to read the title, content and excerpt of any other user's private, draft, pending, scheduled or trashed post.
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.3/10CVSS 4.3
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 26 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.9.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-118188
Is CVE-2026-118188 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-118188?
PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes: from 3.9.0 before 4.3.1.Source: cve.now feed data
How do I fix CVE-2026-118188?
Upgrade to a fixed version: 4.3.1.Source: cve.now feed data