VulnerabilityPublished 10 Oct 2025Updated 14 Oct 2025

CVE-2025-52647: HCL Software BigFix WebUI · Improper Neutralization of HTTP Headers for Scripting Syntax

Affects HCL Software BigFix WebUISource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 10:12 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 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Oct 2025
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
HCL Software BigFix WebUI	Affected =11	Fixed in–

AI-suggested

To mitigate CVE-2025-52647, organizations should implement the following specific measures: 1) Apply any available patches or updates from HCL Software as soon as they are released. 2) If patches are not yet available, configure web application firewalls (WAFs) or reverse proxies to validate and sanitize incoming Host headers, rejecting or rewriting suspicious or unexpected values. 3) Implement strict allowlists for acceptable Host header values based on known domain names and IP addresses used by BigFix WebUI. 4) Monitor web server and application logs for unusual Host header values or patterns indicative of Host Header Poisoning attempts. 5) Educate users about phishing risks and the dangers of clicking on suspicious links that could trigger this vulnerability. 6) Review and harden session management and password reset mechanisms to ensure they do not rely solely on Host header values. 7) Conduct regular security assessments and penetration tests focusing on HTTP header manipulation to detect similar weaknesses. These targeted actions go beyond generic advice by focusing on controlling and validating the Host header and strengthening related application logic.

Description

The BigFix WebUI application responds with HOST information from the HTTP header field making it vulnerable to Host Header Poisoning Attacks.

Impact

For European organizations, this vulnerability poses a risk primarily to the confidentiality and integrity of data managed through BigFix WebUI. Since BigFix is widely used for endpoint management, security patching, and compliance enforcement, exploitation could allow attackers to redirect users to malicious sites, poison caches, or hijack sessions, potentially leading to unauthorized access or data leakage. Organizations in sectors such as finance, healthcare, energy, and government, which rely heavily on endpoint security and compliance tools, could face increased risk of targeted attacks leveraging this vulnerability. The requirement for user interaction means phishing or social engineering campaigns could be used to exploit it. Although availability is not impacted, the indirect effects of compromised endpoint management could disrupt security operations and incident response capabilities. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits over time.

CWE-644Improper Neutralization of HTTP Headers for Scripting Syntax (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes web scripting syntax in HTTP headers that can be used by web browser components that can process raw headers, such as Flash.
Architecture and Design
Perform output validation in order to filter/escape/encode unsafe data that is being passed from the server in an HTTP response header.
Architecture and Design
Disable script execution functionality in the clients' browser.
OWASP Cheat Sheets
Content Security Policy (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
Query Parameterization (opens in a new tab)
OWASP ASVS 4.0.3
V14.4.6 (opens in a new tab)
V14.4.4 (opens in a new tab)
V14.4.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0124562 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Oct 2025, 00:57 UTC

WeaknessesCWE-644

Technical details

References

Community reviews

Related threats