Skip to main content
VulnerabilityPublished

CVE-2026-41575: th30d4y IP · Cross-site Scripting

Affects th30d4y IPSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium : upgrade to 2.0.1 when convenient.

Data as of 30 Oct 2026, 11:52 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 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.1
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 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade IP and th30d4y/IP to 2.0.1.

Affected software

ProductAffectedFixed in
th30d4yIPAffected
  • >=1.0.1 <2.0.1
Fixed in
  • 2.0.1
GitHubth30d4y/IPpkg:github/th30d4y/IPOther threatsAffected
  • >=1.0.1 <2.0.1
Fixed in
  • 2.0.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade the th30d4y IP Reputation Checker application to version 2.0.1 or later, where this vulnerability has been patched. No other specific mitigations are indicated. Patch status is confirmed by the vendor's versioning information in the advisory.

Description

In th30d4y/IP from version 1.0.1 to before version 2.0.1, a DOM-Based Cross-Site Scripting (XSS) vulnerability was identified in an IP Reputation Checker application. Unsanitized user input was directly rendered in the browser, allowing attackers to execute arbitrary JavaScript. This issue has been patched in version 2.0.1.

References

Community reviews

Loading reviews…