In Casdoor versions 2.362.0 and earlier, the SAML service provider implementation does not validate the AudienceRestriction element in SAML assertions. The buildSp function in object/saml_sp.go never sets AudienceURI on the gosaml2 SAMLServiceProvider struct and never inspects WarningInfo.NotInAudience. This allows assertions issued for other service providers to be accepted by Casdoor.
Security readout for executives and security teams
Plain-English summary
Casdoor can accept SAML login assertions meant for a different service provider. For organizations using Casdoor for SAML authentication, this is a critical identity-control failure because it can undermine who is allowed to sign in and what access they receive.
Executive priority
Prioritize this as urgent for any Casdoor-backed SSO environment. It affects identity assurance, could permit unauthorized access, and may impact many downstream applications that trust Casdoor authentication.
Technical view
Casdoor 2.362.0 and earlier do not validate SAML AudienceRestriction. The buildSp function in object/saml_sp.go does not set AudienceURI on gosaml2 SAMLServiceProvider and does not inspect WarningInfo.NotInAudience, so assertions issued for other service providers may be accepted.
Likely exposure
Exposure is likely where Casdoor 2.362.0 or earlier is deployed as a SAML service provider. Risk is higher for internet-facing identity services, shared identity providers, or environments with multiple SAML service providers.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability is still high urgency because the CVSS is 9.8 and the issue affects authentication trust decisions without requiring prior access.
Researcher notes
The evidence identifies a missing AudienceRestriction validation path, specifically unset AudienceURI and ignored NotInAudience warnings. Public data provided does not include exploit details, patch commit, fixed release, or proof of active exploitation.
Mitigation direction
Inventory Casdoor deployments and confirm whether any run version 2.362.0 or earlier.
Check Casdoor and CERT guidance for the fixed version or approved remediation.
Treat affected SAML logins as high risk until vendor remediation is applied.
Review authentication logs for unusual SAML sign-ins or unexpected service-provider context.
Restrict access to affected Casdoor instances where operationally possible.
Validation and detection
Confirm Casdoor version and whether SAML service provider functionality is enabled.
Review SAML integrations for multiple service providers sharing an identity provider.
Verify remediation against vendor guidance once a fixed version is identified.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-863 · source CWE mapping
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.