# CVE-2019-25480: ARMBot Unrestricted File Upload via upload.php

> Unauthenticated attackers can upload arbitrary PHP files to the web root via path traversal in upload.php, achieving remote code execution.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/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:** 11 Mar 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-9mfj-w336-px2g

## What is CVE-2019-25480?

CVE-2019-25480 is a high-severity vulnerability in ARMBot, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ARMBot contains an unrestricted file upload vulnerability in upload.php that allows unauthenticated attackers to upload arbitrary files by manipulating the file parameter with path traversal sequences. Attackers can upload PHP files with traversal payloads ../public_html/ to write executable code to the web root and achieve remote code execution.

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

## Which versions are affected by CVE-2019-25480?


## How do I fix CVE-2019-25480?

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

## Is CVE-2019-25480 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25480 and fix it if it is affected.

What it is: CVE-2019-25480 is a high-severity vulnerability in ARMBot, published on 11 Mar 2026. 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-2019-25480 exists.

Affected product: ARMBot. 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-2019-25480/ (Markdown: https://insights.sbomify.com/CVE-2019-25480/index.md)
```

## Sources

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

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