CVE-2026-8980
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 · uneditedThe Mennekes Amtron series (firmware versions ≤ 5.22.3) is vulnerable to privilege escalation. An authenticated low-privileged user can change the passwords of the admin (operator) and manufacturer accounts via crafted POST requests.
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 Mennekes Amtron EV charging station firmware versions 5.22.3 and earlier contains a privilege escalation vulnerability where an authenticated low-privileged user can change the passwords of admin (operator) and manufacturer accounts via crafted POST requests. This allows a standard user to gain full administrative control over the 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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 the device and confirm it's an Amtron EV charging stationAccess the device's web interface via its IP address, or check the device's management console for product identification. Look for 'Amtron' branding or check the device model/firmware information page.Affected if The device is a Mennekes Amtron EV charging station with a web management interface.
-
Determine the installed firmware versionLog into the web interface and navigate to the firmware or system information page (often under Settings, System, or About). Alternatively, check via the device's administrative console or SNMP if available.Affected if The firmware version is 5.22.3 or lower.
-
Verify the web interface is accessible over the networkAttempt to access the device's IP address on common web ports (HTTP port 80, HTTPS port 443). Confirm the login page loads.Affected if The web management interface is reachable from untrusted networks.
-
Check for presence of multiple user privilege rolesLog into the web interface with an account and navigate to User Management or User Administration settings. Look for roles such as admin, operator, and manufacturer.Affected if Multiple privilege levels (admin/operator and manufacturer) are configured on the device.
-
Review for signs of unauthorized password modificationsCheck the user management logs or audit logs for password change events, especially those initiated by low-privilege accounts. Look for unexpected modifications to admin or manufacturer accounts.Affected if Password changes to higher-privilege accounts were performed without authorization.
A user is affected if they operate a Mennekes Amtron charging station running firmware version 5.22.3 or lower with its web interface accessible and multiple privilege levels configured.
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 dataUpgrade Mennekes Amtron firmware to a version beyond 5.22.3 and restrict network access to charging stations to minimize attack surface.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8980 — 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-8980 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