# CVE-2025-0867: Privilege Escalation in MEAC300

> Hardcoded administrator credentials allow standard users to execute arbitrary commands with administrative privileges, leading to privilege escalation.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 14 Feb 2025
- **Updated:** 21 Feb 2025
- **Also known as:** GHSA-5gcv-59gg-xc7c

## What is CVE-2025-0867?

CVE-2025-0867 is a critical vulnerability in SICK MEAC300, published on 14 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The standard user uses the run as function to start the MEAC applications with administrative privileges. To ensure that the system can startup on its own, the credentials of the administrator were stored. Consequently, the EPC2 user can execute any command with administrative privileges. This allows a privilege escalation to the administrative level.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2025-0867 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0867 is a critical vulnerability in SICK MEAC300, published on 14 Feb 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-0867 in the wild and no public exploit code.

Affected product: SICK MEAC300. 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-0867/ (Markdown: https://insights.sbomify.com/CVE-2025-0867/index.md)
```

## Sources

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

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