PublishPress Permissions unauthenticated broken access control in WordPress plugin
- Exploited
- No known exploitation
- Fix
- Fixed in 5.0.2
- Who is exposed
- Not reported
Summary
The PublishPress Permissions plugin for WordPress (package press-permit-core) has a missing authorization flaw that lets an attacker exploit incorrectly configured access control levels. It can be reached remotely over the network without logging in.
Written by a model
Original description
Missing Authorization vulnerability in PublishPress PublishPress Permissions press-permit-core allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects PublishPress Permissions: from n/a through 5.0.1.
What to do
Upgrade to a fixed version: 5.0.2.
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-131785 (WordPress PublishPress Permissions plugin <= 5.0.1 - 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-131785 (entry last updated 2026-11-20):
Affected:
- PublishPress PublishPress Permissions: fixed in 5.0.2
Fixed versions: 5.0.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131785 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131785 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/press-permit-core/vulnerability/wordpress-publishpress-permissions-plugin-5-0-1-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-131785
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-131785"}.Affected versions
- press-permit-corefixed in 5.0.2 · through 5.0.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 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-131785 |
| Record | NVD · CVE-2026-131785 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/press-permit-core/vulnerability/wordpress-publishpress-permissions-plugin-5-0-1-broken-access-control-vulnerability?_s_id=cve |
Questions about CVE-2026-131785
Is CVE-2026-131785 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-131785?
press-permit-core: through 5.0.1 (fixed in 5.0.2).
Source: cve.now feed data
How do I fix CVE-2026-131785?
Upgrade to a fixed version: 5.0.2.
Source: cve.now feed data
Related
- CVE-2026-84771WordPress PublishPress Permissions plugin <= 4.8.3 - Insecure Direct Object References (IDOR) vulnerability
- CVE-2026-122676WordPress PublishPress Authors plugin <= 4.18.0 - SQL Injection vulnerability
- CVE-2026-94487WordPress PublishPress Capabilities plugin <= 2.50.1 - Cross Site Request Forgery (CSRF) vulnerability
- CVE-2026-66630WordPress PublishPress Series plugin <= 3.1.3 - SQL Injection vulnerability
- CVE-2026-48197WordPress PublishPress Capabilities plugin <= 2.45.0 - Privilege Escalation vulnerability
- CVE-2026-75927PublishPress Capabilities <= 2.50.0 - Authenticated (Editor+) Privilege Escalation to Fresh-Install Default Capability Grant
No corrections so far. Something wrong on this page? Report an error.