Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed SAML ACS endpoint
-
DeliveryCraft SAMLResponse with target NameID
-
ExploitAttach malformed signature forcing OpenSSL -1
-
ExecutionLoose check treats error as valid
-
PersistAuth cookie set for admin account
-
ImpactFull Joomla site compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Exploitation requires that the target Joomla site have one of the vulnerable miniOrange SAML SSO extensions installed and enabled as a Service Provider with an exposed Assertion Consumer Service endpoint - this is the extension's normal operating mode, so no non-default configuration is needed. The attacker must know or guess a valid Joomla username/NameID for the account to impersonate (administrator usernames are often predictable). Limiting factors: the vulnerable SSO extension must actually be active (a Joomla site without these extensions is unaffected), and the ACS endpoint must be reachable by the attacker. No authentication (PR:N), no user interaction (UI:N), and no special client platform are required. |
| Impact | This is a genuine top-priority issue rather than a high-CVSS-but-low-risk artifact: the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N with high confidentiality, integrity, and availability impact) aligns exactly with the description of a remote, unauthenticated, single-request bypass that grants administrator access. No EPSS score, KEV listing, or SSVC decision data was provided, so exploitation-probability and automatability signals are unavailable and cannot corroborate or contradict the severity - but the low technical bar and full-admin outcome mean any exposed, vulnerable instance should be treated as urgent even for a mid-sized operator with a small IT team. The main uncertainty is deployment exposure, not exploitability: the bug is deterministic and requires no special access, so absence of a published POC should not be read as low real-world risk. |
| Exploit ScenarioDerived | An attacker crafts a SAMLResponse asserting NameID 'admin' (or any target Joomla account) and attaches a deliberately malformed signature value that causes openssl_verify() to return -1 rather than 0. They POST it directly to the extension's ACS endpoint over the network without any credentials; the loose check accepts the error as valid, an auth cookie is set for the targeted account, and the attacker gains administrator access. No public POC has been identified, but the single-request, no-authentication nature makes weaponization straightforward. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
Unauthenticated authentication bypass in miniOrange's SAML Single Sign-On extensions for Joomla (SAML SSO < 11.0.2, SAML SP Login with ADFS < 6.4, and SAML SSO login with Google Apps < 6.4) lets remote attackers log in as any Joomla account, including administrators. The mo_saml_validate_signature() function treats OpenSSL's -1 error return as a successful signature verification, so a crafted SAMLResponse with an attacker-chosen NameID and a deliberately malformed signature bypasses validation entirely. Rated CVSS 4.0 10.0; no public exploit identified at time of analysis, but the flaw is trivially reachable and yields full site takeover.
RemediationAI
Upgrade to fixed releases: SAML SSO for Joomla 11.0.2 or later, and both SAML SP Login with ADFS and SAML SSO login with Google Apps 6.4 or later, as implied by the affected-version ranges (verify exact patched builds with the vendor at https://www.miniorange.com/ since no dedicated advisory URL was supplied). If immediate patching is not possible, restrict access to the extension's SAML Assertion Consumer Service (ACS) endpoint - for example by IP-allowlisting your identity provider or placing the login endpoint behind a WAF rule - or temporarily disable the affected SSO extension and fall back to local Joomla authentication; the trade-off is that legitimate SSO logins will break or be limited to known IdP source addresses until the patch is applied.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages 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 components are Joomla extensions that act as SAML Service Providers, consuming SAML assertions from identity providers such as ADFS or Google Apps to authenticate users. Signature validation of the SAML assertion is the sole security control preventing forged identities. PHP's openssl_verify() is tri-state: it returns 1 for a valid signature, 0 for an invalid signature, and -1 when an error occurs during processing. The vulnerable mo_saml_validate_signature() uses a loose boolean check, and because -1 is truthy in PHP, any input that forces OpenSSL into an error path is accepted as a valid signature. This is the root cause behind the CWE-639 (authorization bypass through user-controlled key/identity) classification: the attacker fully controls the asserted NameID and can force the error condition, so the SP trusts an identity it never actually verified.
Know when OpenSSL 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Remote, unauthenticated, single-request bypass (AV:N/AC:L/PR:N/UI:N) yielding full administrator takeover, so C/I/A all High; scope Unchanged as compromise stays within the Joomla application.
Primary rating from Vendor (Joomla).
CVSS VectorVendor: Joomla
DescriptionCVE.org
Joomla Extension - miniorange.com - Unauthenticated Authentication Bypass via SAMLResponse Parameter in miniOrange SAML SSO < 11.0.2, SAML SP Single Sign On - Login with ADFS < 6.4, SAML SP Single Sign On - SAML SSO login with Google Apps < 6.4 - This is due to the mo_saml_validate_signature() function performing a loose boolean check on the raw tri-state integer returned by PHP's openssl_verify(), causing an error return value of -1 to be evaluated as truthy and therefore treated as a successful signature verification. This makes it possible for unauthenticated attackers to log in as any existing Joomla user, including administrators, by submitting a crafted SAMLResponse containing an attacker-controlled NameID and a deliberately malformed signature value that triggers an OpenSSL processing error - bypassing verification entirely and resulting in wp_set_auth_cookie() being called for the targeted account.
Articles & Coverage 2
Executive ViewAI
miniOrange's SAML SSO extensions for Joomla (versions below 11.0.2, 6.4) contain a critical unauthenticated authentication bypass allowing remote attackers to assume any user account, including administrator access, without valid credentials. Organizations deploying affected SAML plugins face immediate risk of complete site compromise, data exfiltration, and malicious system modifications. This vulnerability creates severe business continuity and regulatory compliance exposure for any Joomla installation relying on miniOrange SAML authentication.
Interim mitigations include: (1) Network segmentation restricting Joomla admin interfaces to specific IP ranges and requiring VPN authentication for remote administration; (2) Real-time audit logging and SIEM alerting on all authentication events, admin account modifications, and privilege escalations with defined incident response procedures; (3) Temporary disabling of affected SAML SSO plugins with immediate fallback to alternative authentication methods during remediation window; (4) Continuous threat detection monitoring for exploitation indicators including unexpected admin account creation, rapid authentication anomalies, and lateral movement patterns.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Rated cri
The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to se
The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k
In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehas
The TLS protocol 1.2 and earlier, when a DHE_EXPORT ciphersuite is enabled on a server but not on a client, does not pro
The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which mak
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
The X509_verify_cert function in crypto/x509/x509_vfy.c in OpenSSL 1.0.1n, 1.0.1o, 1.0.2b, and 1.0.2c does not properly
A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Rated hig
EUVD-2026-65476
GHSA-mp5v-46h8-gw29
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB