# CVE-2025-41664: Improper Permission Handling Enables Unauthorized Access to Firmware and Certificates

> A low-privileged remote attacker can access firmware and certificates due to improper permission handling, enabling privilege escalation and firmware modification.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/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:** 8 Sep 2025
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-fr5v-wr5v-rf59

## What is CVE-2025-41664?

CVE-2025-41664 is a high-severity missing authorization vulnerability in WAGO Coupler 0750-0362, published on 8 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A low-privileged remote attacker could gain unauthorized access to critical resources, such as firmware and certificates, due to improper permission handling during the runtime of services (e.g., FTP/SFTP). This access could allow the attacker to escalate privileges and modify firmware.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2025-41664 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41664 is a high-severity missing authorization vulnerability in WAGO Coupler 0750-0362, published on 8 Sep 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-41664 in the wild and no public exploit code.

Affected product: WAGO Coupler 0750-0362. 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-41664/ (Markdown: https://insights.sbomify.com/CVE-2025-41664/index.md)
```

## Sources

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

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