Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-22963 is a high-severity CSRF (CWE-352) vulnerability in Sismics Teedy. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-22963, published on 2025-01-13, is a Cross-Site Request Forgery (CSRF) vulnerability (CWE-352) in Teedy through version 1.11. The issue enables account takeover through a POST request to the /api/user/admin endpoint, with a CVSS v3.1 base score of 7.5 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H).
An unauthenticated attacker (PR:N) with network access (AV:N) can exploit this by tricking a logged-in user into performing an action, such as visiting a malicious webpage (UI:R), despite the high attack complexity (AC:H). Successful exploitation allows full account takeover, granting high impacts on confidentiality, integrity, and availability (C:H/I:H/A:H) with no change in scope (S:U).
Mitigation guidance and patches are detailed in the provided references, including the Teedy blog at https://blog.teedy.io/, analysis at https://github.com/samplev45/CVE-2025-22963, release notes for v1.11 at https://github.com/sismics/docs/releases/tag/v1.11, and a proof-of-concept at https://github.com/sota70/teedy-v1.11-csrf. Practitioners should consult these for upgrade paths beyond version 1.11.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-3057
Vulnerability Data
Teedy through 1.11 allows CSRF for account takeover via POST /api/user/admin.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.3.2V3.5.1V10.2.1
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.
Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.
Contextual intelligence about emerging CSRF toolkits can be translated into updated anti-CSRF token or same-site policy configurations across applications.