dbcve.org
Blu Ic2 FirmwareOperating system · Azure Access

CVE-2025-12363

HIGH · 7.5 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to 1.20 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Email Password Disclosure.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

The vulnerability allows email passwords to be disclosed in plaintext in the BLU-IC2 and BLU-IC4 industrial controllers through version 1.19.5. This could expose authentication credentials to unauthorized parties through insecure storage, transmission, or logging of email-related configuration data.

MitigationUpgrade BLU-IC2 and BLU-IC4 firmware beyond version 1.19.5 to obtain the patch. If upgrading is not immediately possible, restrict network access to these devices and review email configuration settings for exposed credentials.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 device model
    Confirm the industrial controller is either BLU-IC2 or BLU-IC4 by checking the device label, web interface, or management console
    Affected if Device is a BLU-IC2 or BLU-IC4 controller
  2. Check firmware version
    Access the device firmware or system information page via the web interface or CLI, then compare the installed version against the 1.20 threshold
    Affected if Firmware version is below 1.20 (1.19.5 or earlier)
  3. Determine if email notification is configured
    Review the email or SMTP configuration section in the device settings to see if email alerts, notifications, or relay features are enabled
    Affected if Email functionality is configured and active on the device
  4. Inspect email configuration for plaintext passwords
    Examine the email server or notification settings for stored credentials - look for password fields that display in plaintext rather than being masked or hashed
    Affected if Password appears in plaintext in the configuration interface or exported configuration files
  5. Review device logs for credential exposure
    Search system, application, and email-related logs for plaintext instances of the configured email password or authentication strings
    Affected if Plaintext email passwords appear in any log files, diagnostic exports, or troubleshooting output

A device is affected if it is a BLU-IC2 or BLU-IC4 running firmware below version 1.20 and has email configuration enabled with exposed plaintext passwords.

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

Upgrade BLU-IC2 and BLU-IC4 firmware beyond version 1.19.5 to obtain the patch. If upgrading is not immediately possible, restrict network access to these devices and review email configuration settings for exposed credentials.

Recommended fix Moderate confidence

Blu Ic2 Firmware 1.20 or later / Blu Ic4 Firmware 1.20 or later

  1. 1. Identify the specific Blu Ic2 or Blu Ic4 device model requiring firmware update.
  2. 2. Download the firmware version 1.20 or later from the official vendor support site (refer to azure-access.com or vendor's support portal).
  3. 3. Review the device's firmware upgrade instructions in the product manual to ensure proper upload procedure.
  4. 4. Back up current device configuration if possible before initiating the firmware update.
  5. 5. Upload and install firmware version 1.20 onto the Blu Ic2 or Blu Ic4 device.
  6. 6. After installation, verify the device is operational and confirm the new firmware version is reported as 1.20 or higher.
  7. 7. Verify that the email password disclosure vulnerability is resolved by confirming credentials are no longer exposed through the affected interfaces.
Caveat Review release notes for firmware 1.20 to check for any configuration changes or feature modifications that may require adjustment

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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