# CVE-2025-53120: Securden Unified PAM Path Traversal In File Upload

> Unauthenticated attackers can exploit path traversal in file upload to place malicious scripts in web directories, achieving remote code execution on the server.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2025
- **Updated:** 25 Aug 2025
- **Also known as:** GHSA-cmv4-9rjr-99h2

## What is CVE-2025-53120?

CVE-2025-53120 is a critical path traversal vulnerability in Securden Unified PAM, published on 25 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A path traversal vulnerability in unauthenticated upload functionality allows a malicious actor to upload binaries and scripts to the server’s configuration and web root directories, achieving remote code execution on the Unified PAM server.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2025-53120 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53120 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53120 is a critical path traversal vulnerability in Securden Unified PAM, published on 25 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53120 exists.

Affected product: Securden Unified PAM. 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-53120/ (Markdown: https://insights.sbomify.com/CVE-2025-53120/index.md)
```

## Sources

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

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