CVE-2023-35835
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 · uneditedAn issue was discovered in SolaX Pocket WiFi 3 through 3.001.02. The device provides a WiFi access point for initial configuration. The WiFi network provided has no network authentication (such as an encryption key) and persists permanently, including after enrollment and setup is complete. The WiFi network serves a web-based configuration utility, as well as an unauthenticated ModBus protocol interface.
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 confidenceThe SolaX Pocket WiFi 3 (versions up to 3.001.02) creates an open, unauthenticated WiFi access point that persists permanently after initial setup. This access point exposes both a web-based configuration interface and an unauthenticated ModBus protocol interface, allowing anyone within WiFi range to access and potentially control the device without any credentials. The combination of permanent unauthenticated network access and protocol interfaces results in critical exposure.
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>= 3.0.0, <= 3.009.03_20230504CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify SolaX Pocket WiFi 3 deviceLocate the physical SolaX Pocket WiFi 3 adapter connected to your solar inverter. Check the device label or the WiFi network it broadcasts for model identification.Affected if The device is a SolaX Pocket WiFi 3 unit
-
Check firmware versionConnect to the device's WiFi network and access the web interface (typically at 192.168.1.1 or via solaxwifi.local), then navigate to the firmware or status page to view the installed version.Affected if Firmware version is >= 3.0.0 and <= 3.009.03_20230504
-
Verify persistent open WiFi access pointScan for WiFi networks with your device or computer. Look for an open (no password) SSID named something like 'SolaX_XXXXXX' or similar that remains broadcast after initial setup is complete.Affected if An open, unauthenticated WiFi network persists after initial setup has finished
-
Confirm unauthenticated web accessConnect to the open WiFi network and open a web browser to the device's IP address. Attempt to access configuration pages without entering any username or password.Affected if The web configuration interface loads and allows full access without any authentication credentials
-
Check ModBus interface accessibilityUsing a ModBus client or tool (such as modpoll or a Python pymodbus script), attempt to connect to the device on port 502 (or the configured ModBus port) over the WiFi network without providing any authentication.Affected if ModBus protocol communication is possible without authentication
You are affected if you have a SolaX Pocket WiFi 3 device with firmware between 3.0.0 and 3.009.03_20230504 that continues to broadcast an open WiFi network with accessible unauthenticated web and ModBus interfaces.
Generated from the published advisory. Verify against your own configuration.
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 dataNetwork isolation (e.g., VLAN segmentation) should be implemented to restrict access to the device's WiFi network. Contact SolaX for firmware updates that either disable the access point post-setup or add authentication. Until a patch is available, monitor for unauthorized access and consider disabling the WiFi functionality if not required.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35835 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-35835 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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