CVE-2026-12281
Auth bypass in Shibboleth WordPress plugin allows forged headers to create/admin accounts.
Is CVE-2026-12281 being exploited?
Not confirmed. CVE-2026-12281 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.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-12281?
CVE-2026-12281 is rated High with a CVSS score of 8.1. 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-12281?
Yes. A fix has been recorded for CVE-2026-12281. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-12281 affect?
CVE-2026-12281 affects Shibboleth WordPress plugin < 2.5.4, WordPress sites using HTTP header identity mode, Deployments with auto account creation + admin role mapping, Sites that do not strip untrusted client headers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-12281?
Upgrade to Shibboleth WP 2.5.4; disable header identity mode or set a spoof key; strip untrusted headers.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can forge HTTP identity headers to authenticate and auto-create accounts as administrators, enabling full site takeover.
Immediate action required
- affected< 2.5.4
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.