Quick answers
- Is CVE-2026-118188 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118188 being exploited in the wild.
- How severe is CVE-2026-118188?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- PublishPress Revisions 3.9.0 to 4.2.0.
- Is there a fix for CVE-2026-118188?
- Yes: fixed in 4.3.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118188 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-118188?
- Check whether you run PublishPress Revisions at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.3.1
Technical details
The plugin's revision-comparison feature returns post content without properly validating whether the requesting user has permission to view the target post. An authenticated user, including one with Subscriber-level privileges, can access the title, content, and excerpt of unpublished posts in any status (private, draft, pending, scheduled, trashed) belonging to other users via insufficient access control on the comparison endpoint.
Affected products
- PublishPress Revisions 3.9.0 to 4.2.0
Timeline
- 2026-11-04: disclosed
- 2026-11-06: advisory