Skip to main content
CVE-2026-1183VulnerabilityPublished

CVE-2026-1183: Botble TransP · XSS or 'Cross-site Scripting'

Affects Botble TransPSource CVE Database V5

0

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Jan 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
BotbleTransPAffected
  • =all versions
Fixed in–
BotbleAthenaAffected
  • =all versions
Fixed in–
BotbleMartfuryAffected
  • =all versions
Fixed in–
BotbleHomzenAffected
  • =all versions
Fixed in–

AI-suggested

1. Implement strict server-side input validation and sanitization for the 'q' parameter on the '/search' endpoint to neutralize any HTML or script content. 2. Apply output encoding to ensure that any user-supplied data rendered in the browser is treated as text, not executable code. 3. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the browser. 4. Monitor web server logs and application behavior for unusual requests targeting the '/search' endpoint or containing suspicious payloads. 5. Educate users and administrators about the risks of clicking unknown links and recognizing phishing attempts. 6. If possible, isolate or restrict access to vulnerable Botble product instances until patches or fixes are available. 7. Engage with Botble vendors or community to track patch releases and apply updates promptly once available. 8. Conduct regular security assessments and penetration tests focusing on input validation and XSS vulnerabilities. 9. Use web application firewalls (WAF) with rules tailored to detect and block XSS payloads targeting the affected endpoints. 10. Review and update incident response plans to include scenarios involving XSS exploitation.

Description

HTML injection vulnerability in multiple Botble products such as TransP, Athena, Martfury, and Homzen, consisting of an HTML injection due to a lack of proper validation of user input by sending a request to '/search' using the 'q' parameter.

References

Community reviews

Loading reviews…