CVE-2025-0276
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 Modern Client Management (MCM) 3.3 and earlier are vulnerable to certain insecure directives within the Content Security Policy (CSP). An attacker could trick users into performing actions by not properly restricting the sources of scripts and other content.
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 Modern Client Management (MCM) versions 3.3 and earlier contain insecure Content Security Policy directives that fail to properly restrict the sources from which scripts and other content can be loaded. This CSP misconfiguration allows attackers to potentially inject malicious scripts via uncontrolled script sources, enabling actions to be performed on behalf of tricked users.
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<= 3.3< 3.4CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify installed BigFix MCM versionCheck the installed version of HCL BigFix Modern Client Management or BigFix Mobile via the software inventory, registry (Windows), or package manager (Linux). Common locations: /opt/BigFix or Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\BigFix or similar.Affected if The installed version is 3.3 or earlier, or the specific version is less than 3.4 for Modern Client Management, or 3.3 or below for BigFix Mobile.
-
Locate web server or application configuration filesFind the configuration files for the BigFix MCM web component. These may include server.xml, web.xml, or custom config files in the MCM installation directory (commonly under /opt/BigFix/MCM or C:\Program Files\BigFix\MCM).Affected if Configuration files exist and the web interface is enabled.
-
Inspect Content Security Policy headersReview the web server or application configuration for Content-Security-Policy HTTP response headers. If direct access to running headers is possible, use a browser dev tools or curl -I against the MCM web portal endpoint to inspect response headers.Affected if CSP headers are present and contain insecure directives such as 'unsafe-inline', 'unsafe-eval', or wildcards (*) in script-src, style-src, or img-src directives.
-
Check script-src and content source allowlistsExamine the CSP configuration for script-src, object-src, and other content directives. Look for overly permissive settings like missing explicit allowlists, use of 'unsafe-inline' within script-src, or missing restrictions on external script sources.Affected if Script sources are not explicitly restricted to trusted domains, or 'unsafe-inline' is present in any content directive allowing uncontrolled script injection.
-
Verify web portal accessibility and configurationIf the MCM web portal is accessible, use browser developer tools or command-line tools (curl, wget) to request the main page and examine the HTTP response headers for CSP definitions.Affected if The web portal responds with CSP headers containing unsafe directives or no explicit restrictions on script sources.
You are affected if the installed version of HCL BigFix Modern Client Management is below 3.4 (or BigFix Mobile is 3.3 or below) AND the application serves Content Security Policy headers containing 'unsafe-inline', 'unsafe-eval', or unrestricted/wildcard script source directives.
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 · scoped3.4
Review and harden the Content Security Policy headers to remove unsafe directives like 'unsafe-inline' or 'unsafe-eval', and implement strict allowlists for script sources and other content types.
BigFix Modern Client Management 3.4 or later
- 1. Verify current BigFix Modern Client Management version by checking the installed software version or accessing the admin console
- 2. Download BigFix Modern Client Management version 3.4 or later from the official HCL support portal at support.hcl-software.com
- 3. Review upgrade documentation and release notes for version 3.4 to understand any prerequisites
- 4. Perform a backup of the current configuration and database
- 5. Execute the upgrade following HCL's documented upgrade procedure for BigFix MCM
- 6. After upgrade, verify the Content Security Policy headers are properly configured and restrict script sources
- 7. Test that the application functions correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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 $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0276 — 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-0276 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