Summary
CVE-2026-75800 is a critical improper authentication vulnerability in the Frontegg SAML SSO plugin for WordPress, versions up to and including 1.0.1. The plugin fails to verify the cryptographic signature or issuer of incoming SAML authentication responses before establishing a user session, allowing a remote, unauthenticated attacker to forge SAML assertions and log in as any existing user — including administrators — or create arbitrary new accounts. The flaw carries a CVSS v3.1 base score of 9.8 (Critical).
Technical details
- Root cause: The plugin’s SAML response handler does not validate the digital signature or the issuer identifier of SAML assertions received from an identity provider (IdP) before trusting the assertion and establishing a WordPress session.
- Trigger conditions: An attacker submits a crafted/forged SAML response to the site’s SAML assertion consumer endpoint; because signature and issuer checks are skipped, the forged assertion is accepted as valid.
- Attack vector: Network-based, requires no authentication and no user interaction (AV:N, PR:N, UI:N).
- Impact: Full authentication bypass and account takeover — an attacker can impersonate any user, including site administrators, and the plugin’s auto-provisioning behavior (creating a new WordPress account from the email address in the SAML assertion) allows attackers to mint arbitrary accounts, including admin-level ones, resulting in complete loss of confidentiality, integrity, and availability of the affected WordPress site.
- CWE classification: CWE-287 (Improper Authentication).
Affected software
- Frontegg SAML SSO WordPress plugin: all versions up to and including 1.0.1
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: No fixed version of the plugin has been released; as of this writing the plugin has been closed/removed from the WordPress.org plugin repository pending review, and no updated release addressing this issue is available.
- If no patch is available:
- Disable and deactivate the Frontegg SAML SSO plugin immediately and revert to native WordPress authentication (or another vetted SSO/SAML solution) until a fixed version is released.
- Audit existing WordPress user accounts, especially administrator accounts, for any unrecognized or recently created users that may indicate prior exploitation.
- Restrict or block external access to the plugin’s SAML assertion consumer service (ACS) endpoint at the network/WAF layer until the plugin is patched or removed.
- Monitor authentication logs for anomalous SAML login events or unexpected account creation activity.

