Skip to main content

SAML Single Sign On EUVDEUVD-2026-83667

| CVE-2026-82842 HIGH
Improper Privilege Management (CWE-269)
2026-09-20 WPScan GHSA-c354-pg28-5955
8.1
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WP site using vulnerable SAML SSO plugin
  2. Delivery
    Obtain ability to shape IdP assertion
  3. Exploit
    Assert target admin's login name in SAML response
  4. Execution
    Plugin links identity by login name only
  5. Persist
    Authenticate as administrator
  6. Impact
    Full site takeover

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires the site to use this plugin for SAML SSO on an affected version (4.8.43 through <6.0.0), and requires the attacker to be able to have the site's Identity Provider assert a login name of the attacker's choosing - for example an IdP that permits self-service registration or user-controlled login-name/username attributes, or a compromised or attacker-operated IdP trusted by the site. The flaw is that the plugin ignores whatever account-linking criterion the admin configured (email, NameID, etc.) and always matches on login name, so no ownership of the target account is proven. Limiting factors: exploitation is unauthenticated at the WordPress layer (PR:N) but is gated by the attacker's degree of control over the trusted IdP's assertions (reflected in CVSS AC:H); sites whose IdP strictly controls the asserted login-name attribute are much harder to exploit.

Impact

This is a genuine high-priority authentication flaw, not a high-CVSS-but-low-risk case. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/C:H/I:H/A:H = 8.1) correctly captures a network-reachable, unauthenticated (PR:N) account takeover with full C/I/A impact - successful exploitation yields administrator access to the WordPress site. The mitigating signal is AC:H, which reflects a real prerequisite: the attacker must be able to make the site's SAML Identity Provider assert an arbitrary login name. A publicly available exploit exists (WPScan) and a vendor patch (v6.0.0) is available, which raises real-world urgency. However, no EPSS score and no CISA KEV listing are present in the provided data, so there is no evidence of confirmed active exploitation or of automated widespread targeting - the difficulty is that exploitation is deployment-specific (it hinges on how much control an attacker has over the IdP assertion), so this is better treated as a targeted rather than mass-exploitation risk. Net: patch promptly given POC availability and admin-level impact, but the AC:H IdP-control precondition limits opportunistic exploitation.

Exploit ScenarioDerived

On a WordPress site using this plugin for SAML SSO where the linking criterion was configured to match on email or NameID, an attacker who controls or can influence assertions from the site's IdP (e.g., a self-service IdP allowing users to set their own login-name attribute, or a compromised/malicious IdP) crafts an assertion carrying the login name of the target administrator. The plugin ignores the configured criterion and resolves purely by login name, logging the attacker in as that administrator without proving ownership. A public exploit is available via WPScan, and the flaw is remotely reachable without a prior WordPress account (PR:N).

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 20, 2026

Authentication bypass in the SAML Single Sign On WordPress plugin (versions 4.8.43 through <6.0.0) lets a remote, unauthenticated attacker log in as any WordPress user, including an administrator. The plugin ignores whatever account-linking criterion the administrator configured (email, NameID, etc.) and always resolves the SAML identity by login name, so an attacker who can get the site's trusted Identity Provider to assert a login name of their choosing - for example via an IdP that allows self-service registration or user-controlled username attributes, or a compromised or attacker-operated IdP - authenticates as that account without proving ownership of it. Publicly available exploit code exists, and while the CVSS vector scores the flaw at 8.1 with PR:N, the AC:H rating reflects the significant prerequisite of influencing the trusted IdP's assertions; sites whose IdP strictly controls the asserted login-name attribute are much harder to exploit.

RemediationAI

Vendor-released patch: upgrade the SAML Single Sign On WordPress plugin to 6.0.0 or later, which is the version that closes the flawed login-name-only account resolution; all versions below 6.0.0, including the confirmed affected 4.8.43 through the 5.x line, should be treated as vulnerable. See the WPScan advisory at https://wpscan.com/vulnerability/4ae66b2c-a0de-405f-baca-127302257540/ and the NVD record at https://nvd.nist.gov/vuln/detail/CVE-2026-82842 for the vendor guidance. If patching must be deferred, the practical compensating controls all centre on the IdP prerequisite that makes exploitation possible: restrict the trusted IdP's assertions so that the login-name attribute cannot be chosen or influenced by the end user (disable self-service registration and user-editable username/login-name or NameID attributes at the IdP), and review any federated/guest IdP trust to ensure only an IdP your organisation fully controls is configured in the plugin - note that this hardens the prerequisite rather than the plugin defect itself, so it fails if an attacker ever gains control of assertion content. As a short-term containment, disable the plugin and fall back to WordPress-native authentication or a manually audited SSO path, accepting the operational and user-experience cost that entails, and audit existing accounts for unexpected logins or role changes while the plugin was unpatched.

Affected VersionsENISA

SAML Single Sign On 4.8.43 <6.0.0

Affected Packages

euvd saml_single_sign_on fix: 6.0.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is the SAML Single Sign On plugin for WordPress, which implements SAML 2.0 service-provider functionality so that an external Identity Provider (IdP) can assert a user's identity and log them into WordPress. WordPress SAML plugins normally let administrators choose how an incoming assertion is linked to an existing account - by email address, by the SAML NameID, or by login name - precisely so that a matching assertion cannot be turned into access to an unrelated account. This plugin fails to honour that configured criterion and always falls back to matching the asserted login name, a classic improper privilege management / access-control defect (CWE-269): the account-selection decision is made on attacker-influencable data (the login-name attribute asserted by the IdP) rather than on the identity that the administrator said should be trusted. Per the assessed CVSS:3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, no authentication at the WordPress layer is required (PR:N) and no user interaction is needed, but the AC:H component captures the real gate: the attacker must be able to have the site's IdP assert a login name of their choosing, which typically means an IdP that permits self-service sign-up or user-controlled username/login-name attributes, or an IdP that is compromised or operated by the attacker. The CPE record (cpe:2.3:a:unknown:saml_single_sign_on:*:*:*:*:*:*:*:*) matches all versions of the plugin, and the EUVD data narrows the confirmed affected range to 4.8.43 through everything below 6.0.0.

Know when Saml Single Sign On gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.1 HIGH

Network-reachable and needs no WordPress account (PR:N/UI:N), but requires control over the IdP-asserted login name (AC:H); success grants admin access, so C/I/A all High.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Sep 20, 2026 - 14:22 NVD
8.1 (HIGH)
Patch available
Sep 20, 2026 - 07:01 EUVD
CVE Published
Sep 20, 2026 - 06:00 cve.org
HIGH 8.1
CVE Published
Sep 20, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The SAML Single Sign On WordPress plugin before 6.0.0 does not honour the configured criterion for linking an incoming single sign-on identity to a WordPress account, always resolving the identity by login name whatever the site has chosen, which allows an attacker who can have the site's identity provider assert a login name of their choosing to authenticate as any account, including an administrator, without proving ownership of that account.

Technical POC Analysis

Bug class as assigned by WPScan: CWE-269, Improper Privilege Management (WPScan type: PRIVESC; OWASP A2, Broken Authentication and Session Management).

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

The SAML Single Sign On WordPress plugin (versions 4.8.43 through 6.0.0) contains an authentication bypass that allows remote unauthenticated attackers to impersonate any user, including administrators, potentially leading to full site compromise. Publicly available exploit code exists, elevating the risk of data breaches and service disruption for organizations relying on this plugin. Leadership should prioritize immediate patching to protect sensitive information and maintain customer trust.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Medium
SAML SSO WordPress plugin; enterprise/SSO deployments only, not universal
Exploit
POC
Public exploit code exists
Social Media
2
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

60
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy