CVE-2025-40679
Unknown Unknown - Not Provided
HTML Injection in Isshue 'product_name' Parameter via POST Request

Publication date: 2026-01-20

Last updated on: 2026-01-20

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

Description
HTML Injection vulnerability in Isshue by Bdtask, consisting os an HTML injection due to a lack os proper validation of user input by sending a POST request to '/category_product_search', affecting the 'product_name' parameter.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-20
Last Modified
2026-01-20
Generated
2026-05-07
AI Q&A
2026-01-20
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
bdtask isshue to 2025-10-01 (exc)
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 Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-40679 is an HTML injection vulnerability in Isshue, an eCommerce platform by Bdtask. It occurs because the application does not properly validate user input in the 'product_name' parameter when a POST request is made to the '/category_product_search' endpoint. This allows attackers to inject malicious HTML code into the web page, potentially leading to security issues such as content manipulation or script execution. [1]


How can this vulnerability impact me? :

This vulnerability can allow attackers to inject malicious HTML into the affected web pages, which may lead to unauthorized content display, phishing attacks, or manipulation of the user interface. Although it does not directly allow code execution or data theft, it can degrade user trust and potentially be leveraged in more complex attacks. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

You can detect this vulnerability by monitoring POST requests sent to the '/category_product_search' endpoint and inspecting the 'product_name' parameter for HTML injection patterns. For example, using curl to send a test POST request with HTML tags in the 'product_name' parameter and observing the response can help identify if the input is improperly validated. A sample command could be: curl -X POST -d "product_name=<script>alert(1)</script>" https://your-target-domain/category_product_search. Additionally, web application scanners that detect HTML injection or cross-site scripting (XSS) vulnerabilities can be used to automate detection. [1]


What immediate steps should I take to mitigate this vulnerability?

Since no official patch or solution has been reported yet, immediate mitigation steps include implementing input validation and sanitization on the 'product_name' parameter to prevent HTML injection. You can also apply web application firewall (WAF) rules to block malicious payloads targeting the '/category_product_search' endpoint. Limiting user input to expected characters and encoding output can reduce the risk until an official fix is available. [1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart