dbcve.org
Blu Ic2 FirmwareOperating system · Azure Access

CVE-2025-12001

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-20
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
Lack of application manifest sanitation could lead to potential stored XSS.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 · moderate confidence

Stored XSS vulnerability in BLU-IC2 and BLU-IC4 industrial controllers due to lack of sanitization on application manifest data. User-supplied input stored in the manifest is rendered without proper encoding, allowing injection of malicious scripts that execute when the manifest is viewed by other users.

MitigationImplement proper input validation and output encoding on all manifest fields; apply vendor firmware update beyond version 1.19.5 when available; if no update exists, consider network segmentation to limit exposure of the management interface.

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. Identify firmware version on BLU-IC2 controller
    Access the controller's management interface or use the vendor-provided diagnostic tool to query the installed firmware version. Common methods include checking the 'About' or 'System Information' page in the web UI, or running a command like 'show version' via CLI if available.
    Affected if Firmware version is less than 1.20 (e.g., 1.19.x, 1.18.x)
  2. Identify firmware version on BLU-IC4 controller
    Access the controller's management interface or use the vendor-provided diagnostic tool to query the installed firmware version. Common methods include checking the 'About' or 'System Information' page in the web UI, or running a command like 'show version' via CLI if available.
    Affected if Firmware version is less than 1.20 (e.g., 1.19.x, 1.18.x)
  3. Determine if management interface is network-accessible
    Check network configuration to verify whether the controller's web-based management interface is exposed to network segments that include other users or untrusted devices. Review firewall rules, ACLs, or network segmentation settings.
    Affected if The management interface is reachable from network segments where other users or untrusted devices reside
  4. Verify if manifest viewing functionality is accessible
    Check if the application manifest feature is enabled and accessible through the management interface. This may involve reviewing user roles, permissions, or feature flags configured on the controller.
    Affected if Users can access the manifest viewing feature and the controller firmware is below version 1.20

A user is affected if their BLU-IC2 or BLU-IC4 controller runs firmware version 1.19.x or lower AND the management interface with manifest viewing capability is accessible to users who could inject malicious script content.

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

Implement proper input validation and output encoding on all manifest fields; apply vendor firmware update beyond version 1.19.5 when available; if no update exists, consider network segmentation to limit exposure of the management interface.

Recommended fix Moderate confidence

Firmware 1.20

  1. Identify the BLU-IC2 or BLU-IC4 device model and current firmware version
  2. Download the firmware version 1.20 or later from the vendor's official support website
  3. Review vendor release notes for any specific upgrade prerequisites or warnings
  4. Follow the vendor's standard firmware update procedure (typically via web UI, USB, or network-based deployment)
  5. After upgrade, verify the new firmware version is 1.20 or later
  6. Test that the application manifest functionality works correctly post-upgrade

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

Fix this in Blu Ic2 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12001 — 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-12001 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