Security readout for executives and security teams
Plain-English summary
Casdoor may continue accepting a JWT for token exchange even after administrators believe that token was revoked. For organizations using Casdoor as an identity provider, this weakens incident response because a stolen or compromised token may remain usable. The provided sources rate this as critical, but do not show confirmed active exploitation.
Executive priority
Prioritize this for identity environments because failed revocation can extend attacker access after compromise. The urgency is highest for internet-facing Casdoor deployments or systems using Casdoor tokens to protect sensitive applications.
Technical view
In Casdoor 2.362.0 and earlier, GetTokenExchangeToken() in object/token_oauth.go validates JWT signature and claims but does not check the Token table for revocation or invalidation state. The issue maps to CWE-613 and has CVSS 3.1 score 9.8. The supplied sources do not identify a specific fixed version.
Likely exposure
Exposure is most likely where Casdoor 2.362.0 or earlier is deployed and OAuth token exchange is enabled or relied upon. Internet-facing identity services increase business impact, but the source bundle does not provide deployment-specific exploit prevalence.
Exploitation context
The source bundle says no KEV listing is present. It describes a logic flaw in revocation enforcement, not an exploit campaign. Do not assume active exploitation without additional vendor, CISA, or incident reporting evidence.
Researcher notes
Evidence is limited to the CVE description and CERT reference in the bundle. The affected range is stated as Casdoor 2.362.0 and earlier. No source-provided patch version, workaround, proof-of-concept, or active exploitation report is included.
Mitigation direction
- Inventory Casdoor deployments and identify versions 2.362.0 or earlier.
- Check Casdoor and CERT guidance for a patched version or approved workaround.
- Reduce external exposure of affected Casdoor services where operationally feasible.
- Treat token revocation as unreliable until vendor remediation is applied.
- Review incident response assumptions for compromised Casdoor tokens.
Validation and detection
- Confirm installed Casdoor versions across production and staging.
- Determine whether OAuth token exchange is used in your Casdoor configuration.
- In a controlled test, verify whether revoked subject tokens are rejected.
- Review logs for suspicious token exchange activity after known revocations.
- Track vendor and CERT updates for fix availability.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-613: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-9097 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://kb.cert.org/vuls/id/780781CVE reference, certcc
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficient Session Expiration
Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.