CVE-2026-27751
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 · uneditedSODOLA SL902-SWTGW124AS firmware versions through 200.1.20 contain a default credentials vulnerability that allows remote attackers to obtain administrative access to the management interface. Attackers can authenticate using the hardcoded default credentials without password change enforcement to gain full administrative control of the device.
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 SODOLA SL902-SWTGW124AS wireless gateway firmware through version 200.1.20 contains hardcoded default administrative credentials that allow remote attackers to authenticate to the management interface without any password change enforcement, granting full administrative control of the device.
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<= 200.1.20CVSS 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 device modelLocate the device physically or via network discovery and confirm it is a SODOLA SL902-SWTGW124AS wireless gateway. Check the device label, web interface header, or SNMP sysDescr for this exact model name.Affected if Device model is SODOLA SL902-SWTGW124AS
-
Determine firmware versionAccess the device management web interface and navigate to the firmware/version information page, or use the command line interface (CLI) via Telnet/SSH if available and run the 'version' or 'show firmware' command.Affected if Firmware version cannot be determined or is <= 200.1.20
-
Compare version to affected rangeReview the obtained firmware version number against the affected range. Versions up to and including 200.1.20 are vulnerable.Affected if Firmware version is 200.1.20 or lower
-
Test for hardcoded default credentialsAttempt to log in to the device management web interface using the default credentials known to be hardcoded in the firmware. If SSH/Telnet is enabled, try these credentials there as well.Affected if Login succeeds with default credentials without requiring a prior password change
-
Verify credential persistenceAfter successfully logging in with default credentials, check if the credentials remain valid even after attempting to change the admin password through the web interface password change function.Affected if Default credentials remain valid after password change attempt, indicating hardcoded credentials
You are affected if the device is a SODOLA SL902-SWTGW124AS with firmware version 200.1.20 or lower, and the management interface is accessible using hardcoded default credentials.
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 dataImmediately change default credentials on all affected devices, apply any available vendor firmware patches, and restrict network access to the management interface via firewall or VLAN segmentation to limit exposure.
- 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-2026-27751 — 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-2026-27751 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