CVE-2025-52621
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHCL 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceHCL BigFix SaaS Authentication Service has a cache poisoning vulnerability where HTTP responses reflect the Origin header without validation. An attacker can manipulate the Origin header value in requests to poison the web cache, potentially causing subsequent users to receive malicious content served from the cache.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 8.1.14CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm HCL BigFix SaaS is deployedIdentify if your environment includes HCL BigFix SaaS product by checking installed software, documentation, or cloud service subscription detailsAffected if The product is HCL BigFix SaaS
-
Check installed versionAccess the BigFix administration console or use the version checking mechanism provided by HCL BigFix to determine the currently installed version numberAffected if Version is lower than 8.1.14
-
Verify Authentication Service is exposedCheck network configuration to confirm the Authentication Service endpoint is externally accessible or shared internallyAffected if Authentication Service is accessible and version is below 8.1.14
-
Inspect HTTP responses for Origin header reflectionSend a request to the Authentication Service with a crafted Origin header (e.g., Origin: http://attacker.com) and examine the response headers and body to see if the Origin value is reflected without validationAffected if Origin header value is reflected in responses without sanitization and version is vulnerable
-
Confirm caching is enabledCheck web server or proxy cache configuration for the Authentication Service to determine if response caching is activeAffected if Caching is enabled and Origin header is reflected in cached responses
You are affected if running HCL BigFix SaaS version below 8.1.14 with the Authentication Service exposed and caching enabled while the Origin header is reflected in responses.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.1.14
Implement validation of the Origin header value before reflecting it in responses, and ensure proper cache key isolation to prevent cache poisoning attacks.
BigFix SaaS version 8.1.14 or later
- Verify current BigFix SaaS version by checking the HCL BigFix console or contacting HCL support
- Contact HCL BigFix SaaS support or your account representative to request upgrade to version 8.1.14 or later
- Confirm with HCL that the upgrade includes the fix for CVE-2025-52621 which addresses the Origin header cache poisoning vulnerability
- After upgrade, verify that HTTP responses no longer reflect the Origin header unvalidated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52621 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-52621 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data