CVE-2025-22368
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 authenticated SCU firmware command of the firmware for Mennekes Smart / Premium Chargingpoints can be abused for command execution because OS commands are improperly neutralized when certain fields are passed to the underlying OS.
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 · moderate confidenceAuthenticated command injection in Mennekes Smart/Premium EV charging station firmware. The SCU firmware's command handling fails to properly neutralize OS command characters in certain input fields, allowing authenticated attackers to execute arbitrary OS commands on the underlying Linux/system.
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
- Low
- Authentication
- Y
- User interaction
- None
- Scope
- N
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:N/SA:N/E:X/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:N/AU:Y/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 charging station modelAccess the charging station's web management interface or check the physical device labeling to confirm it is a Mennekes Smart or Premium EV charging station model.Affected if The device is a Mennekes Smart or Premium EV charging station.
-
Locate the SCU firmware componentCheck the firmware version or system information within the charging station management interface, typically found under 'System Info', 'About', or 'Firmware Version' sections. Look for references to SCU firmware.Affected if The device runs SCU firmware (SCU is the station controller unit).
-
Verify authentication is enabledCheck the security or access control settings in the charging station management interface. Confirm that user authentication is required for accessing command/input fields.Affected if Authentication is disabled or uses weak/default credentials, allowing unauthorized access to input fields.
-
Inspect input fields for command handlingAccess the command or configuration input fields in the management interface. Test whether special characters like ; | & $ ` ( ) are filtered or passed to the underlying OS by entering a benign test command.Affected if Input fields accept and execute OS command characters without sanitization, indicating the vulnerability is present.
-
Review system logs for command injection evidenceExamine the charging station's system logs, typically accessible via the management interface under 'Logs' or 'Diagnostics', for suspicious commands or unexpected script executions.Affected if Logs show unauthorized or unexpected OS command executions originating from authenticated sessions.
You are affected if you have a Mennekes Smart/Premium EV charging station running SCU firmware where authenticated users can inject OS commands through input fields that lack proper character sanitization.
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 update when available; restrict network access to charging station management interfaces; ensure strong authentication credentials; network segment charging infrastructure.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22368 — 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-2025-22368 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