dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-22366

HIGH · 8.7 CVSS v4.0 Published 2025-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
The authenticated firmware update capability of the firmware for Mennekes Smart / Premium Chargingpoints can be abused for command execution because OS command 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 confidence

The vulnerability exists in the authenticated firmware update mechanism of Mennekes Smart and Premium electric vehicle charging stations. Attackers with valid authentication credentials can inject OS commands through certain input fields that are passed to the underlying operating system without proper sanitization, leading to arbitrary command execution on the charging point device.

MitigationImplement strict input validation and proper neutralization of all user-supplied fields before passing them to OS command execution functions in the firmware update process. Restrict firmware update authentication and consider network segmentation for these critical charging infrastructure devices.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the charging station model
    Locate the device label or access the admin interface to confirm the model is Mennekes Smart or Premium variant
    Affected if The device is a Mennekes Smart or Premium electric vehicle charging station
  2. Determine the installed firmware version
    Access the device admin panel or use the manufacturer's diagnostic tool to retrieve the current firmware version number
    Affected if The installed firmware version falls within the affected range (compare your version to vendor advisories)
  3. Verify firmware update functionality status
    Check the admin interface or configuration settings to see if the firmware update mechanism is enabled
    Affected if Firmware update feature is enabled and accessible
  4. Confirm authentication configuration
    Review user accounts and access control settings for the firmware update interface to verify what credentials are configured
    Affected if Valid authentication credentials exist for firmware update access
  5. Assess network exposure of update interface
    Check firewall rules, network segmentation, and access control lists to determine if the firmware update interface is reachable from network segments
    Affected if The firmware update interface is exposed on the network without proper network isolation

You are affected if you have a Mennekes Smart or Premium charging station with an enabled firmware update interface and your firmware version matches the affected range per vendor documentation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and proper neutralization of all user-supplied fields before passing them to OS command execution functions in the firmware update process. Restrict firmware update authentication and consider network segmentation for these critical charging infrastructure devices.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22366 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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