# CVE-2025-59776: AutomationDirect Productivity Suite Relative Path Traversal

> Unauthenticated remote attackers can exploit a relative path traversal flaw to create arbitrary directories on the target machine via the PLC simulator.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2025
- **Updated:** 24 Oct 2025
- **Also known as:** GHSA-79jv-p4w2-qgx9

## What is CVE-2025-59776?

CVE-2025-59776 is a medium-severity path traversal vulnerability in AutomationDirect Productivity 1000 P1-540 CPU, published on 23 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A relative path traversal vulnerability was discovered in Productivity Suite software version 4.4.1.19. The vulnerability allows an unauthenticated remote attacker to interact with the ProductivityService PLC simulator and create arbitrary directories on the target machine.

Weakness: CWE-23 (Relative Path Traversal)

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


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

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

## Is CVE-2025-59776 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59776 is a medium-severity path traversal vulnerability in AutomationDirect Productivity 1000 P1-540 CPU, published on 23 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59776 in the wild and no public exploit code.

Affected product: AutomationDirect Productivity 1000 P1-540 CPU. 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-59776/ (Markdown: https://insights.sbomify.com/CVE-2025-59776/index.md)
```

## Sources

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

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