dbcve.org
Improper Certificate ValidationWeakness · CWE-295

CVE-2025-15573

CRITICAL · 9.4 CVSS v3.1 Published 2026-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The affected devices do not validate the server certificate when connecting to the SolaX Cloud MQTTS server hosted in the Alibaba Cloud (mqtt001.solaxcloud.com, TCP 8883). This allows attackers in a man-in-the-middle position to act as the legitimate MQTT server and issue arbitrary commands to devices.

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

SolaX Cloud MQTT devices fail to validate the server certificate when connecting to the SolaX Cloud MQTTS server (mqtt001.solaxcloud.com, TCP 8883). This allows an attacker in a man-in-the-middle position to impersonate the legitimate MQTT server and send arbitrary commands to devices.

MitigationContact SolaX for firmware updates that implement proper SSL/TLS certificate validation. In the interim, network segment devices to limit exposure to MITM attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

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 the device model and type
    Locate the device label, documentation, or management interface to confirm it is a SolaX Cloud MQTT-enabled solar/battery device
    Affected if The device is a SolaX Cloud MQTT product
  2. Verify connection to the affected endpoint
    Capture network traffic or review device configuration to confirm it connects to mqtt001.solaxcloud.com on TCP port 8883
    Affected if The device connects to mqtt001.solaxcloud.com:8883
  3. Inspect TLS certificate validation behavior
    Use a TLS test tool or proxy to attempt a MITM test; observe whether the device accepts a certificate not signed by a trusted CA
    Affected if The device accepts connections without validating the server certificate
  4. Check the current firmware version
    Access the device management interface or API to retrieve the installed firmware version number
    Affected if The firmware version predates any SolaX patch for CVE-2025-15573

A user is affected if they operate a SolaX Cloud MQTT device that connects to mqtt001.solaxcloud.com on port 8883 without proper TLS server certificate validation implemented in their current firmware.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Contact SolaX for firmware updates that implement proper SSL/TLS certificate validation. In the interim, network segment devices to limit exposure to MITM attacks.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
42.0 hours of engineering $7,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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