CVE-2025-22963 json
Teedy through 1.11 allows CSRF for account takeover via POST /api/user/admin.
published last yr. modified 4mo ago also EUVD-2025-3057
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
Teedy through 1.11 allows CSRF for account takeover via POST /api/user/admin.
Patch / fix
Is CVE-2025-22963 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Sismics Teedy
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/sota70/teedy-v1.11-csrf
broken-link
-
blog.teedy.io
/
broken-link
-
github.com
/sismics/docs/releases/tag/v1.11
release-notes
-
github.com
/samplev45/CVE-2025-22963
third-party-advisory
Sources
- CVE List CVE-2025-22963
- NVD CVE-2025-22963
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.