# CVE-2025-41667: Phoenix Contact: File access due to the replacement of a critical file used by the arp-preinit script

> A low-privileged remote attacker can replace a critical script file to gain full read, write, and execute access on Phoenix Contact industrial devices.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/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 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-7327-v742-4qwr

## What is CVE-2025-41667?

CVE-2025-41667 is a high-severity path traversal vulnerability in PHOENIX CONTACT AXC F 1152, published on 8 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A low privileged remote attacker with file access can replace a critical file used by the arp-preinit script to get read, write and execute access to any file on the device.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2025-41667 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41667 is a high-severity path traversal vulnerability in PHOENIX CONTACT AXC F 1152, published on 8 Jul 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-41667 in the wild and no public exploit code.

Affected product: PHOENIX CONTACT AXC F 1152. 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-41667/ (Markdown: https://insights.sbomify.com/CVE-2025-41667/index.md)
```

## Sources

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

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