Skip to main content
VulnerabilityPublished Updated

CVE-2025-22963: Sismics Teedy · Cross-Site Request Forgery (CSRF)

Affects Sismics TeedySource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Sismics TeedyAffected
  • =0
Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Immediately review and restrict access to the /api/user/admin endpoint, limiting it to trusted IP ranges or VPNs where feasible. 2) Implement robust anti-CSRF tokens in all state-changing requests, ensuring that the server validates these tokens before processing. 3) Enforce strict Content Security Policy (CSP) headers to reduce the risk of malicious cross-origin requests. 4) Educate users about the risks of phishing and the importance of not clicking on suspicious links, as user interaction is required for exploitation. 5) Monitor logs for unusual POST requests to the vulnerable endpoint, especially those originating from unexpected sources or with anomalous payloads. 6) If possible, isolate Teedy instances in segmented network zones to limit lateral movement in case of compromise. 7) Stay updated with vendor advisories for patches or updates addressing this vulnerability and apply them promptly once available. 8) Consider implementing Web Application Firewalls (WAF) with rules to detect and block CSRF attack patterns targeting the affected endpoint.

Description

Teedy through 1.11 allows CSRF for account takeover via POST /api/user/admin.

References

Community reviews

Loading reviews…