CVE-2025-11853: Sismics Teedy · Improper Access Controls
Affects Sismics TeedySource CVE Database V5
Public exploit available · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 16 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Sismics Teedy | Affected
| Fixed in– |
AI-suggested
Organizations should immediately assess their use of Sismics Teedy versions 1.0 through 1.11 and consider the following mitigations: 1) Restrict network access to the Teedy API endpoint (/api/file) by implementing firewall rules or network segmentation to limit exposure to trusted internal networks only. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious API requests targeting access control bypass attempts. 3) Monitor logs for unusual access patterns or unauthorized API calls to detect potential exploitation attempts early. 4) If possible, disable or restrict the vulnerable API endpoint until a vendor patch or official fix is available. 5) Consider migrating to alternative document management solutions with active security support if vendor remediation is not forthcoming. 6) Implement strict access controls and least privilege principles on the server hosting Teedy to minimize damage in case of exploitation. 7) Regularly back up critical data to enable recovery from potential data integrity attacks. 8) Stay updated on vendor announcements or community patches and apply them promptly once available.
Description
A vulnerability was determined in Sismics Teedy up to 1.11. This affects an unknown function of the file /api/file of the component API Endpoint. Executing a manipulation can lead to improper access controls. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.