dbcve.org
Blu Ic2 FirmwareOperating system · Azure Access

CVE-2025-11925

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-17
Fix available
A fix is available. Upgrade to 1.20 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Incorrect Content-Type header in one of the APIs (`text/html` instead of `application/json`) replies may potentially allow injection of HTML/JavaScript into reply.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.

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 · high confidence

The BLU-IC2 and BLU-IC4 APIs return an incorrect Content-Type header (`text/html` instead of `application/json`) in certain API responses. This MIME type mismatch can allow injection of HTML/JavaScript into responses, potentially leading to Cross-Site Scripting (XSS) attacks if browsers or clients incorrectly parse the response as HTML.

MitigationConfigure the affected API endpoints to return the correct `application/json` Content-Type header. Additionally, implement client-side validation to verify the Content-Type header matches the expected response format before processing.

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
Blu Ic2 FirmwareOperating system
Affected:< 1.20
Blu Ic4 FirmwareOperating system
Affected:< 1.20

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

Work through these to decide whether this CVE applies to you.

  1. Check BLU-IC2 firmware version
    Access the device management interface or API and retrieve the firmware version for the BLU-IC2 module
    Affected if Firmware version is below 1.20
  2. Check BLU-IC4 firmware version
    Access the device management interface or API and retrieve the firmware version for the BLU-IC4 module
    Affected if Firmware version is below 1.20
  3. Inspect API response Content-Type headers
    Send a request to the BLU-IC2 or BLU-IC4 API endpoints and examine the Content-Type header in the response
    Affected if The Content-Type header is set to text/html instead of application/json for API responses
  4. Verify JSON API responses for HTML content
    Make API calls to the affected endpoints and inspect the response body; check if HTML tags, scripts, or unexpected markup appear in what should be JSON responses
    Affected if The response body contains HTML or JavaScript content when the endpoint should return JSON data

A system is affected if either the BLU-IC2 or BLU-IC4 firmware is version below 1.20 AND the API returns incorrect Content-Type headers or HTML content in JSON responses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.20 or later
Fixed in 1.20
Interim mitigation

Configure the affected API endpoints to return the correct `application/json` Content-Type header. Additionally, implement client-side validation to verify the Content-Type header matches the expected response format before processing.

Recommended fix Moderate confidence

BLU-IC2 and BLU-IC4 Firmware version 1.20

  1. 1. Identify the current firmware version of the BLU-IC2 or BLU-IC4 device
  2. 2. Navigate to the device's administrative interface or use the vendor's firmware update mechanism
  3. 3. Download the firmware version 1.20 or later from the vendor's official support site
  4. 4. Apply the firmware update following the vendor's documented upgrade procedure
  5. 5. Verify the update was successful and confirm the device is running firmware version 1.20 or higher
  6. 6. Test the affected API endpoint to verify the Content-Type header now returns 'application/json' instead of 'text/html'
Caveat Review vendor release notes for any configuration or behavioral changes between versions 1.19.x and 1.20

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Blu Ic2 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11925 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11925 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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