# CVE-2025-22369: Mennekes smart/premium charges systems, Arbitrary file download using ReadFile endpoint

> Attackers can read arbitrary files from the operating system via the ReadFile endpoint in Mennekes charging stations.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/S:N/AU:Y`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2025
- **Updated:** 1 Apr 2025
- **Also known as:** GHSA-45j7-2qxv-qg3v

## What is CVE-2025-22369?

CVE-2025-22369 is a high-severity path traversal vulnerability in Mennekes Smart / Premium charging stations, published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The ReadFile endpoint of the firmware for Mennekes Smart / Premium Chargingpoints can be abused to read arbitrary files from the underlying OS.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2025-22369?


## How do I fix CVE-2025-22369?

No fix has been published for CVE-2025-22369 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-22369 being exploited?

There is no known exploitation of CVE-2025-22369 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22369 and fix it if it is affected.

What it is: CVE-2025-22369 is a high-severity path traversal vulnerability in Mennekes Smart / Premium charging stations, published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-22369 in the wild and no public exploit code.

Affected product: Mennekes Smart / Premium charging stations. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-22369/ (Markdown: https://insights.sbomify.com/CVE-2025-22369/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22369
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22369
- OSV: https://osv.dev/vulnerability/CVE-2025-22369

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-22369/
Summaries are generated and may contain mistakes; the official description above is the record.