# CVE-2026-103752: WordPress Authorizer plugin <= 3.15.3 - Privilege Escalation vulnerability

> Unauthenticated attackers can escalate privileges in the Authorizer WordPress plugin, allowing unauthorized access to higher-level user roles.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-jhwc-r696-2xmf

## What is CVE-2026-103752?

CVE-2026-103752 is a critical vulnerability in Paul Ryan Authorizer, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated Privilege Escalation in Authorizer <= 3.15.3 versions.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

No fix has been published for CVE-2026-103752 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103752 being exploited?

There is no known exploitation of CVE-2026-103752 in the wild and no public exploit code.

Public exploit code:

- Defensive analysis, patch breakdown, and passive detection scanner for CVE-2026-103752 (WordPress Authorizer Plugin <= 3.15.3). (github_poc): https://github.com/anoxhunterdump-ctrl/CVE-2026-103752-Authorizer-Privilege-Escalation

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103752 and fix it if it is affected.

What it is: CVE-2026-103752 is a critical vulnerability in Paul Ryan Authorizer, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103752 in the wild and no public exploit code.

Affected product: Paul Ryan Authorizer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103752/ (Markdown: https://insights.sbomify.com/CVE-2026-103752/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103752
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103752
- OSV: https://osv.dev/vulnerability/CVE-2026-103752

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103752/
Summaries are generated and may contain mistakes; the official description above is the record.