Skip to main content
VulnerabilityPublished

CVE-2026-30162: Timo · Cross-site Scripting

Affects TimoSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 10:12 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Mar 2026

  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
GitHubauntvt/Timopkg:github/auntvt/TimoOther threatsAffected
  • =2.0.3
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-2026-30162, organizations should implement strict input validation and sanitization on the title field to ensure that no executable scripts or malicious HTML can be injected. Employing context-aware output encoding (e.g., HTML entity encoding) when rendering user-supplied data is critical to prevent script execution. Web Application Firewalls (WAFs) can be configured to detect and block common XSS attack patterns targeting the title field. Until an official patch is released, consider disabling or restricting the use of the title field for user input or applying manual content review processes. Educate users to avoid clicking suspicious links and implement Content Security Policy (CSP) headers to limit the execution of unauthorized scripts. Regularly monitor security advisories from the Timo software maintainers for updates or patches. Conduct security testing, including automated scanning and manual penetration testing, to identify and remediate similar vulnerabilities. Finally, maintain robust incident response plans to quickly address any exploitation attempts.

Description

Cross Site Scripting (xss) vulnerability in Timo 2.0.3 via crafted links in the title field.

References

Community reviews

Loading reviews…