CVE-2026-1183
Unknown Unknown - Not Provided

HTML Injection in Botble Products via /search?q Parameter

Vulnerability report for CVE-2026-1183, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-01-20

Last updated on: 2026-01-20

Assigner: Spanish National Cybersecurity Institute, S.A. (INCIBE)

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-01-20
Last Modified
2026-01-20
Generated
2026-07-06
AI Q&A
2026-01-20
EPSS Evaluated
2026-07-05
NVD
EUVD

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
botble transp *
botble athena *
botble martfury *
botble homzen *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-1183 is an HTML injection vulnerability found in multiple Botble products such as TransP, Athena, Martfury, and Homzen. It occurs because the 'q' parameter in requests sent to the '/search' endpoint does not properly validate user input, allowing attackers to inject malicious HTML code into the web page. [1]

Impact Analysis

This vulnerability can allow attackers to inject malicious HTML into the affected web applications, potentially leading to issues such as content manipulation, phishing, or other attacks that exploit the injected HTML. Since it requires user interaction (UI:A), the impact depends on users visiting crafted URLs or submitting malicious input. [1]

Detection Guidance

You can detect this vulnerability by sending HTTP requests to the '/search' endpoint with the 'q' parameter containing HTML tags or scripts to see if the input is improperly reflected without sanitization. For example, using curl: curl -G 'http://target-site/search' --data-urlencode 'q=<script>alert(1)</script>' and observing if the response includes the injected HTML or script. This indicates the presence of the HTML injection vulnerability. [1]

Mitigation Strategies

Since no official patch or solution has been reported yet, immediate mitigation steps include implementing input validation and sanitization on the 'q' parameter at the application level to prevent HTML injection. Additionally, consider applying web application firewall (WAF) rules to block malicious payloads targeting the '/search' endpoint and monitor for suspicious requests. [1]

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-1183. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart