dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-22367

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 time setting 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

Authenticated command injection vulnerability in Mennekes Smart/Premium charging station firmware. The time setting function improperly neutralizes user input when passed to OS command execution, allowing authenticated attackers to execute arbitrary OS commands.

MitigationRestrict network access to the charging station management interface to trusted IPs only, and apply vendor firmware updates when available. Consider network segmentation for EV charging infrastructure.

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 device model
    Access the charging point web management interface or check physical device labeling to confirm it is a Mennekes Smart or Premium Charging Point model
    Affected if Device is a Mennekes Smart or Premium Charging Point
  2. Determine firmware version
    Log into the web management interface and navigate to System Info or Settings to find the firmware version. Compare against any released patch versions from Mennekes.
    Affected if Firmware version is unpatched and predates the vendor fix
  3. Verify web management interface accessibility
    Check if the charging point web interface is reachable on the network. The time setting functionality is typically accessed via HTTP/HTTPS.
    Affected if Web interface is network-accessible and time setting feature is enabled
  4. Confirm authentication is required
    Attempt to access the time setting page without credentials or verify that authentication is enforced for administrative functions
    Affected if Authentication is not enforced or default credentials are in use
  5. Check for signs of command injection
    Review system logs or diagnostic exports for unexpected commands, unusual scheduled tasks, or unfamiliar processes that may indicate prior exploitation
    Affected if Logs show unexpected OS commands or suspicious processes related to time settings

A user is affected if they have an unpatched Mennekes Smart/Premium Charging Point firmware with the web management interface exposed and the time setting functionality accessible to authenticated users.

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

Restrict network access to the charging station management interface to trusted IPs only, and apply vendor firmware updates when available. Consider network segmentation for EV charging infrastructure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22367 — 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-22367 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