Skip to content

WebCritical 9.8

CVE-2026-103752

Unauthenticated privilege escalation in Authorizer WordPress plugin <=3.15.3.

How scary is it?

updated 22 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • Yes

    Proof-of-concept code is public2

    1 GitHub proof of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list3

    Not in the catalog as of our last sync.

Scare-o-meter

Act this week

Serious and within reach of attackers. Schedule the fix this week.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: Reachable over the network with no login and no user action; CVSS 9.8.1 Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run Paul Ryan Authorizer in an affected version<= 3.15.3

    The CVE record states no fixed release.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Recommendation, AI-writtenDisable/remove Authorizer or restrict access; apply vendor patch when released.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Unauthenticated privilege escalation in a widely deployed WordPress plugin could allow mass site takeovers and is broadly impactful.

CVSS
9.8Criticalscored by the publisher (CNA)
Exploited in the wild
Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS
0.32%chance of exploitation in the next 30 daystop 75% of scored CVEsFIRST score of 21 Nov 2026
Fix
Not stated by the vendorno fixed release in the CVE record
Published
1 Oct 2026analysed here 2 Oct 2026

Summary

Impact

Unauthenticated attackers can escalate to admin, create/control accounts, and fully compromise WordPress sites.

Triage

Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
No. See why

Executive summary (AI-written)

CVE-2026-103752 represents a severe vulnerability within the Authorizer plugin for WordPress, rated at a CVSS score of 9.8. This means that unauthenticated attackers can exploit this vulnerability to escalate their privileges to that of an admin, allowing them to create or control user accounts and potentially take full control of any compromised WordPress site. Given the widespread use of this plugin across various industries, the implications could be catastrophic, leading to mass takeovers of websites and significant reputational damage for affected organizations. Immediate action is essential to mitigate this risk, particularly as no official patch is currently available.

Technical analysis (AI-written)

The vulnerability identified as CVE-2026-103752 is categorized as an unauthenticated privilege escalation flaw within the Authorizer WordPress plugin, affecting versions up to 3.15.3. This flaw allows an attacker to escalate privileges without prior authentication, which implies that any malicious user can leverage this vulnerability to gain administrative access to a WordPress site using the affected plugin. The CVSS score of 9.8 categorizes this vulnerability as critical, indicating a potential for widespread exploitation. The primary attack vector for this vulnerability is through crafted requests that exploit the underlying logic of the Authorizer plugin. Attackers may use automated tools to scan for vulnerable installations and deploy payloads that trigger the privilege escalation. Given the high impact and ease of exploitation, the complexity of an attack is low, making it likely that even low-skilled attackers could execute successful exploitation attempts. Currently, there is no patch available from the vendor to remediate this vulnerability, raising the urgency for immediate action from site administrators. The recommended mitigation strategies include disabling or completely removing the Authorizer plugin until a vendor patch can be applied. Additionally, site administrators should consider restricting access to their WordPress admin panel, or implementing further security measures such as firewalls or two-factor authentication. In preparation for when a patch becomes available, organizations should monitor the vendor’s communications closely and implement a change management process to apply the updates promptly. Furthermore, a review of existing user accounts and privileges is advisable to ensure that no unauthorized access has been gained while the vulnerability remains unaddressed. Finally, compliance with best practices for securing WordPress installations and plugins will enhance overall security posture against similar vulnerabilities in the future.

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.

Affected products

ProductAffected versions
Paul Ryan Authorizer<= 3.15.3Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • Authorizer WordPress plugin <=3.15.3
  • WordPress sites using Authorizer plugin

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? No. The vulnerability allows unauthenticated privilege escalation via the WordPress plugin, likely through normal HTTP requests without unusual patterns, so a WAF cannot reliably distinguish malicious from legitimate requests.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
CISA SSVC
exploitation none, automatable yes, technical impact totalAssessed by CISA 1 Oct 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 1 Oct 2026Published
  2. 1 Oct 2026CISA SSVC assessment: exploitation nonesame day later
  3. 1 Oct 2026CVE record last updatedsame day later
  4. 2 Oct 2026First proof-of-concept repository on GitHub (unvetted)same day later
  5. 2 Oct 2026Analysed by vulneraibility.com1 day later

Common questions

Is CVE-2026-103752 being exploited?

Not confirmed. CVE-2026-103752 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.

How severe is CVE-2026-103752?

CVE-2026-103752 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-103752?

Not known from our data. No patch reference has been recorded for CVE-2026-103752, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-103752 affect?

CVE-2026-103752 affects Authorizer WordPress plugin <=3.15.3, WordPress sites using Authorizer plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-103752?

Disable/remove Authorizer or restrict access; apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

1 reference in the CVE record, grouped by the tags the record gives them.

Other links (1)

  • patchstack.com /database/wordpress/plugin/authorizer/vulnerability/wordpress-authorizer-plugin-

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.