CVE-2024-46278: teedy · Cross-site Scripting
Affects teedySource CVE Database V5
Not known to be exploited · public exploit available (Exploit-DB) · CVSS 8.4 High.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 2.8% chance of exploitation in 30 days – higher than 86% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 7 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
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
Timeline
CVE ID reserved
by MITRE Corporation
, 26 days before disclosure
CVE published
on cve.org
, t = 0
First Exploit-DB entry (opens in a new tab)
Teedy 1.11 - Account Takeover via Stored Cross-Site Scripting (XSS)
, 191 days after disclosure
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
| Product | Affected | Fixed in |
|---|---|---|
GitHubayato-shitomi/teedypkg:github/ayato-shitomi/teedyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-46278, organizations should first restrict access to the Teedy management console to trusted administrators only, implementing strict network segmentation and access controls such as VPNs or zero-trust network architectures. Employ multi-factor authentication (MFA) to reduce the risk of credential compromise. Monitor user activities and audit logs for unusual behavior indicative of attempted exploitation. Since no official patches are currently available, consider applying temporary mitigations such as input validation and output encoding at the web application firewall (WAF) level to block malicious payloads targeting the management console. Engage with the Teedy community or vendor to obtain updates or patches as soon as they are released. Additionally, educate administrators about the risks of XSS and safe browsing practices within the management console. Conduct regular security assessments and penetration testing focused on the management interface to identify and remediate similar vulnerabilities proactively.
Description
Teedy 1.11 is vulnerable to Cross Site Scripting (XSS) via the management console.