VulnerabilityPublished 12 Feb 2026

CVE-2025-15574: SolaX Power Pocket WiFi 3.0 · Weak Randomness

Affects SolaX Power Pocket WiFi 3.0Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.022.03 when convenient.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.022.03, 1.009.02, 1.005.05 +2

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
SolaX PowerPocket WiFi 3.0	Affected <3.022.03	Fixed in 3.022.03
SolaX PowerPocket WiFi+LAN	Affected <1.009.02	Fixed in 1.009.02
SolaX PowerPocket WiFi+4GM	Affected <1.005.05	Fixed in 1.005.05
SolaX PowerPocket WiFi+LAN 2.0	Affected <006.06	Fixed in 006.06
SolaX PowerPocket WiFi 4.0	Affected <003.03	Fixed in 003.03

AI-suggested

To mitigate this vulnerability, organizations should immediately upgrade all affected SolaX Power Pocket WiFi 3.0 devices to firmware version 3.022.03 or later once available, as this should address the weak password derivation mechanism. Until patches are deployed, restrict physical and digital access to device registration numbers to prevent attackers from obtaining these credentials. Implement network-level controls such as IP whitelisting or VPN access for connections to the Solax Cloud MQTT server to limit unauthorized access. Monitor MQTT server logs for unusual authentication attempts or device impersonation activities. Consider deploying anomaly detection systems to identify suspicious inverter behavior or data inconsistencies. Engage with SolaX Power support to confirm patch availability and request guidance on secure credential management. Additionally, review and enhance overall IoT device security policies, including device inventory management and credential confidentiality practices, to reduce exposure to similar risks.

Description

When connecting to the Solax Cloud MQTT server the username is the "registration number", which is the 10 character string printed on the SolaX Power Pocket device / the QR code on the device. The password is derived from the "registration number" using a proprietary XOR/transposition algorithm. Attackers with the knowledge of the registration numbers can connect to the MQTT server and impersonate the dongle / inverters.

Impact

The primary impact of this vulnerability is the potential for attackers to impersonate legitimate SolaX Power Pocket WiFi 3.0 devices and their associated inverters by exploiting weak authentication credentials. This impersonation can lead to unauthorized access to the Solax Cloud MQTT server, enabling attackers to inject false telemetry data, disrupt inverter operations, or manipulate energy production reporting. Such actions could undermine the integrity of energy management systems, cause operational disruptions, and potentially lead to financial losses or grid instability if exploited at scale. Confidentiality is moderately impacted since attackers gain unauthorized access to device communications, but availability is not directly affected. Organizations relying on these devices for solar power monitoring and control may face risks to operational reliability and trust in their energy data. The ease of exploitation—requiring only knowledge of the registration number—raises the likelihood of targeted attacks, especially if registration numbers are exposed or leaked. The absence of known exploits in the wild suggests limited current impact but highlights the need for proactive mitigation.

CWE-330Use of Insufficiently Random Values (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds.
Implementation
Consider a PRNG that re-seeds itself as needed from high quality pseudo-random output sources, such as hardware devices.
Architecture and Design · Requirements · Libraries or Frameworks
Use products or modules that conform to FIPS 140-2 to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
Attack patterns
Signature Spoofing by Key Recreation (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
Brute Force (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

r.sec-consult.com/solax (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Feb 2026, 14:09 UTC

WeaknessesCWE-330

Technical details

References

Community reviews

Related threats