CVE-2025-52621VulnerabilityPublished 15 Aug 2025Updated 18 Aug 2025

CVE-2025-52621: HCL Software BigFix SaaS Remediate · Origin Validation Error

Affects HCL Software BigFix SaaS RemediateSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 8.1.14 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.1.14

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
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: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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: None: There is no loss of integrity within 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 15 Aug 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 2026-10-26.

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 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

Upgrade HCL Software BigFix SaaS Remediate to 8.1.14.

Affected software

Product	Affected	Fixed in
HCL Software BigFix SaaS Remediate	Affected <8.1.14	Fixed in 8.1.14

AI-suggested

European organizations using HCL BigFix SaaS Remediate should take the following specific mitigation steps: 1) Monitor HCL Software advisories closely for official patches or updates addressing CVE-2025-52621 and apply them promptly once available. 2) In the interim, implement strict HTTP response header controls at the web application firewall (WAF) or reverse proxy level to sanitize or remove the Origin header from responses to prevent unvalidated reflection. 3) Employ cache-control headers to limit caching of sensitive responses, such as setting 'Cache-Control: no-store' or 'private' to reduce the risk of poisoned cache entries. 4) Conduct thorough security testing and code review of any custom integrations or extensions interacting with the BigFix SaaS Authentication Service to ensure no additional origin validation flaws exist. 5) Enhance monitoring and logging for unusual HTTP header patterns or cache anomalies that could indicate attempted exploitation. 6) Educate security teams about the nature of cache poisoning attacks to improve detection and incident response readiness. These measures go beyond generic patching advice by focusing on HTTP header management and cache policies tailored to the specific vulnerability vector.

Description

HCL BigFix SaaS Authentication Service is vulnerable to cache poisoning. The BigFix SaaS's HTTP responses were observed to include the Origin header. Its presence alongside an unvalidated reflection of the Origin header value introduces a potential for cache poisoning.

Impact

For European organizations, this vulnerability poses a risk primarily to the confidentiality of sensitive information managed through the BigFix SaaS platform. Since BigFix is commonly used in large enterprises and government institutions for endpoint management, successful exploitation could lead to unauthorized disclosure of data or manipulation of cached responses that might facilitate further attacks. Although the direct impact on integrity and availability is not indicated, the potential for cache poisoning could be leveraged in multi-stage attacks targeting European organizations' internal networks or cloud environments. Given the reliance on SaaS platforms and the increasing adoption of cloud-based endpoint management in Europe, the vulnerability could affect organizations across various sectors including finance, healthcare, manufacturing, and public administration. The medium severity suggests that while immediate catastrophic damage is unlikely, the vulnerability should be addressed promptly to prevent exploitation, especially in environments with high compliance requirements such as GDPR. Additionally, the lack of required privileges and user interaction lowers the barrier for attackers, increasing the risk profile for organizations that have not yet updated to fixed versions.

CWE-346Origin Validation Error (opens in a new tab)
Class weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not properly verify that the source of data or communication is valid.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V14.5.2 (opens in a new tab)
V14.5.3 (opens in a new tab)
V1.4.4 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cache Poisoning (opens in a new tab)
DNS Cache Poisoning (opens in a new tab)
Exploit Script-Based APIs (opens in a new tab)
Application API Message Manipulation via Man-in-the-Middle (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=KB0123330 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Aug 2025, 01:03 UTC

WeaknessesCWE-346

Technical details

References

Community reviews

Related threats