VulnerabilityPublished 20 Jan 2026

CVE-2025-40679: Bdtask Isshue · XSS or 'Cross-site Scripting'

Affects Bdtask IsshueSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 17:16 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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Active
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: Low
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Active: Successful exploitation of this vulnerability requires a targeted user to perform specific, conscious interactions with the vulnerable system and the attacker’s payload, or the user’s interactions would actively subvert protection mechanisms which would lead to exploitation of the vulnerability.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
BdtaskIsshue	Affected =all versions	Fixed in–

AI-suggested

To mitigate CVE-2025-40679, organizations should implement multiple layers of defense: 1) Apply strict input validation and sanitization on the 'product_name' parameter to ensure no HTML or script content is accepted. Use allowlists for acceptable characters and encode output appropriately. 2) Employ context-aware output encoding (e.g., HTML entity encoding) before rendering user input in web pages to prevent script execution. 3) Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce impact of XSS. 4) Conduct regular security code reviews and automated scanning to detect injection flaws. 5) Educate users and administrators about phishing and suspicious links to reduce the risk from user interaction requirements. 6) Monitor web application logs for unusual POST requests to '/category_product_search' that may indicate exploitation attempts. 7) If available, update to patched versions of Isshue once released by Bdtask. 8) Consider deploying Web Application Firewalls (WAFs) with rules to detect and block XSS payloads targeting the vulnerable parameter. 9) Limit exposure of the vulnerable endpoint by restricting access or implementing additional authentication layers if feasible. 10) Maintain an incident response plan to quickly address any exploitation events.

Description

CVE-2025-40679 is a medium-severity Cross-Site Scripting (XSS) vulnerability in the Bdtask Isshue product affecting all versions. The flaw arises from improper input validation of the 'product_name' parameter in POST requests to '/category_product_search', allowing HTML injection. Exploitation requires no authentication but does require user interaction, such as clicking a crafted link or submitting malicious input. While no known exploits are currently reported in the wild, successful attacks could lead to session hijacking, defacement, or redirection to malicious sites. European organizations using Isshue should prioritize patching or applying mitigations to prevent exploitation. Countries with higher adoption of Isshue or e-commerce platforms relying on it are at greater risk. Mitigations include input validation, output encoding, Content Security Policy enforcement, and user awareness training. The CVSS score of 5.1 reflects moderate risk due to network attack vector and no privileges required but user interaction needed.

Impact

For European organizations using Isshue, this vulnerability poses a moderate risk primarily to web application users and administrators. Exploitation could allow attackers to execute arbitrary scripts in users’ browsers, potentially leading to session hijacking, credential theft, or unauthorized actions within the application. This can undermine user trust, cause reputational damage, and lead to regulatory compliance issues under GDPR if personal data is compromised. E-commerce or content platforms relying on Isshue may experience customer impact or financial losses due to fraud or downtime caused by exploitation. Although the vulnerability does not directly affect system availability or integrity, the indirect consequences of successful XSS attacks—such as phishing or malware distribution—can be significant. The requirement for user interaction limits mass exploitation but targeted attacks against high-value users or administrators remain a concern. The lack of known exploits in the wild reduces immediate urgency but does not eliminate risk, especially as attackers often develop exploits post-disclosure. Organizations in Europe must consider the risk in the context of their user base size, exposure of the affected endpoints, and the sensitivity of data processed by Isshue.

Summary

CVE-2025-40679 identifies a Cross-Site Scripting (XSS) vulnerability classified under CWE-79 in the Isshue product developed by Bdtask. This vulnerability stems from improper neutralization of user-supplied input during web page generation, specifically in the 'product_name' parameter processed via POST requests to the '/category_product_search' endpoint. Because the application fails to properly validate or sanitize this input, an attacker can inject arbitrary HTML or JavaScript code. When a victim interacts with the malicious input—such as by visiting a crafted URL or submitting manipulated form data—the injected script executes in the victim's browser context. This can lead to a range of impacts including theft of session cookies, user impersonation, unauthorized actions, or redirection to malicious websites. The vulnerability affects all versions of Isshue, indicating a systemic issue in input handling. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N) indicates the attack can be launched remotely over the network without authentication, requires low attack complexity, but does require user interaction. There is no impact on confidentiality, integrity, or availability directly, but the scope is limited to the user's browser session. No patches or known exploits are currently documented, but the vulnerability's presence in all versions necessitates proactive mitigation. The vulnerability was reserved in April 2025 and published in January 2026 by INCIBE, reflecting a responsible disclosure timeline. Given the nature of XSS, attackers could leverage this flaw for phishing, session hijacking, or delivering malware payloads through the affected web application.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
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.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

incibe.es/en/incibe-cert/notices/aviso-sci/html-injection-isshue-bdtask (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Jan 2026, 20:25 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats