Paul Ryan Authorizer privilege escalation in user role checks
- Exploited
- No known exploitation
- Fix
- Fixed in 3.17.2
- Who is exposed
- Not reported
Summary
Paul Ryan's Authorizer plugin for WordPress has a flaw that lets an attacker gain higher privileges than they should have. It can be reached remotely, without logging in, and needs no action from a user.
Written by a model
Original description
Incorrect Privilege Assignment vulnerability in Paul Ryan Authorizer authorizer allows Privilege Escalation.This issue affects Authorizer: from n/a before 3.17.2.
What to do
Upgrade to a fixed version: 3.17.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-129056 (WordPress Authorizer plugin < 3.17.2 - Privilege Escalation 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-129056 (entry last updated 2026-11-20):
Affected:
- Paul Ryan Authorizer: fixed in 3.17.2
Fixed versions: 3.17.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129056 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129056 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/authorizer/vulnerability/wordpress-authorizer-plugin-3-17-2-privilege-escalation-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-129056
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-129056"}.Affected versions
- authorizerfixed in 3.17.2
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129056 |
| Record | NVD · CVE-2026-129056 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/authorizer/vulnerability/wordpress-authorizer-plugin-3-17-2-privilege-escalation-vulnerability?_s_id=cve |
Questions about CVE-2026-129056
Is CVE-2026-129056 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
What does this mean?
A low-privilege user can become an admin and gain full control of the site.
Source: patchstack.com
Which versions are affected by CVE-2026-129056?
authorizer: before 3.17.2.
Source: cve.now feed data
Am I affected, and how do I check?
The advisory lists the Authorizer WordPress plugin by Paul Ryan, versions before 3.17.2, as affected. The installed version can be checked on the WordPress Plugins screen.
Source: patchstack.com
How do I fix CVE-2026-129056?
Update the Authorizer plugin to version 3.17.2 or later, which the vendor's advisory names as the fix.
Source: patchstack.com
Related
- CVE-2026-103752WordPress Authorizer plugin <= 3.15.3 - Privilege Escalation vulnerability
- CVE-2026-81294WordPress Authorizer plugin <= 3.15.1 - Privilege Escalation vulnerability
- CVE-2026-125769WordPress Advanced Form Integration plugin <= 2.11.3 - Privilege Escalation vulnerability
- CVE-2026-129255CoolerMaster MASTERPLUS+ Device Driver WinRing0x64.sys sub_11504 default permission
- CVE-2026-133015In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via boot classpath libraries in the Kotlin DSL sandbox
- CVE-2026-69187WeGIA: Authenticated Privilege Escalation due to Missing Action-level Authorisation
No corrections so far. Something wrong on this page? Report an error.