PublishPress Revisions access control bypass in revision permissions
- Exploited
- No known exploitation
- Fix
- Fixed in 4.3.4
- Who is exposed
- Not reported
Summary
The PublishPress Revisions plugin for WordPress has a missing authorization flaw that lets an attacker exploit incorrectly configured access control levels, with a low impact on confidentiality. The flaw can be reached remotely over the network by someone with a low-privilege login, and it needs no action from another user.
Written by a model
Original 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.3.3.
What to do
Upgrade to a fixed version: 4.3.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131730 (WordPress PublishPress Revisions plugin <= 4.3.3 - Broken Access Control vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131730 (entry last updated 2026-11-20):
Affected:
- PublishPress PublishPress Revisions: fixed in 4.3.4
Fixed versions: 4.3.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131730 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131730 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/revisionary/vulnerability/wordpress-publishpress-revisions-plugin-4-3-3-broken-access-control-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131730
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131730"}.Affected versions
- revisionaryfixed in 4.3.4 · through 4.3.3
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.3/10CVSS 4.3
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
Timeline
- CVE published
- Record last updated
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131730 |
| Record | NVD · CVE-2026-131730 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/revisionary/vulnerability/wordpress-publishpress-revisions-plugin-4-3-3-broken-access-control-vulnerability?_s_id=cve |
Questions about CVE-2026-131730
Is CVE-2026-131730 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: cve.now feed data
Which versions are affected by CVE-2026-131730?
revisionary: through 4.3.3 (fixed in 4.3.4).
Source: cve.now feed data
How do I fix CVE-2026-131730?
Upgrade to a fixed version: 4.3.4.
Source: cve.now feed data
Related
- CVE-2026-32539WordPress PublishPress Revisions plugin <= 3.7.23 - SQL Injection vulnerability
- CVE-2024-9436PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 3.5.14 - Reflected Cross-Site Scripting
- CVE-2026-25322WordPress PublishPress Revisions plugin <= 3.7.22 - Cross Site Request Forgery (CSRF) vulnerability
- CVE-2026-120851WordPress PublishPress Revisions plugin <= 4.2.0 - Broken Access Control vulnerability
- CVE-2024-11154PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes <= 3.5.15 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure
- CVE-2026-122676WordPress PublishPress Authors plugin <= 4.18.0 - SQL Injection vulnerability
No corrections so far. Something wrong on this page? Report an error.