# CVE-2026-82842: SAML Single Sign On < 6.0.0 - Unauthenticated Privilege Escalation via Account Matching

> Attackers can authenticate as any user, including administrators, by exploiting flawed SAML identity matching logic in the WordPress plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 20 Sep 2026
- **Updated:** 20 Sep 2026
- **Also known as:** GHSA-c354-pg28-5955

## What is CVE-2026-82842?

CVE-2026-82842 is a high-severity authentication bypass vulnerability in Unknown SAML Single Sign On, published on 20 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-82842 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82842 is a high-severity authentication bypass vulnerability in Unknown SAML Single Sign On, published on 20 Sep 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-82842 in the wild and no public exploit code.

Affected product: Unknown SAML Single Sign On. 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-82842/ (Markdown: https://insights.sbomify.com/CVE-2026-82842/index.md)
```

## Sources

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

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