Quick answers
- Is CVE-2026-118187 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118187 being exploited in the wild.
- How severe is CVE-2026-118187?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- PublishPress Revisions before 4.3.1.
- Is there a fix for CVE-2026-118187?
- 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-118187 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-118187?
- 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 lacks proper access control verification when processing post duplication requests, checking only that the user can edit posts of that type rather than verifying permission to access the specific post being duplicated. This insecure direct object reference (IDOR) allows users with contributor or higher privileges to duplicate private, draft, pending, or scheduled posts into their own workspace and read the full content. The vulnerability requires an authenticated user with at least contributor-level access.
Affected products
- PublishPress Revisions before 4.3.1
Timeline
- 2026-11-06: disclosed: Public vulnerability disclosure
- 2026-11-04: advisory: WPScan entry published