CVE-2018-25134
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 · uneditedSynaccess netBooter NP-02x/NP-08x 6.8 contains an authentication bypass vulnerability in the webNewAcct.cgi script that allows unauthenticated attackers to create admin user accounts. Attackers can exploit the missing control check by sending crafted POST requests to create administrative accounts and gain unauthorized control over power supply management.
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 Synaccess netBooter NP-02x/NP-08x version 6.8 contains an authentication bypass vulnerability in the webNewAcct.cgi script. The script lacks proper authentication control checks, allowing unauthenticated attackers to send crafted POST requests that create administrative user accounts. This grants full unauthorized control over the power supply management device.
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
- 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 modelAccess the device web interface or check the device label/serial to confirm it is a Synaccess netBooter NP-02x or NP-08x modelAffected if Device is not an NP-02x or NP-08x model
-
Check firmware versionLog into the device web interface and navigate to the firmware or status page to view the installed firmware version, or use the device's CLI if availableAffected if Firmware version is 6.8
-
Confirm webNewAcct.cgi is presentAttempt to access http://<device-ip>/cgi-bin/webNewAcct.cgi via a GET request to verify the script exists on the deviceAffected if The script returns a response rather than a 404 error
-
Review user accounts for unauthorized entriesLog into the device as an administrator and navigate to the user management or account settings page to list all defined administrative accountsAffected if Unexpected or unknown administrative accounts exist beyond those intentionally created
-
Inspect HTTP logs for exploitation attemptsReview device logs or any accessible HTTP access logs for POST requests to webNewAcct.cgi, particularly with parameters indicating account creationAffected if Recent POST requests to webNewAcct.cgi are present in logs
A user is affected if they have a Synaccess netBooter NP-02x/NP-08x device running firmware version 6.8 with the web interface accessible and either unexpected admin accounts exist or POST requests to webNewAcct.cgi are found in logs
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 dataApply vendor firmware patch if available; if no patch exists, implement network segmentation and firewall rules to restrict access to the device's web management interface to trusted IP addresses only.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-25134 — 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-2018-25134 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