# CVE-2025-23051: Authenticated Remote Code Execution in AOS Web-based Management Interface

> Authenticated attackers can inject parameters to overwrite system files and execute code on HPE Aruba AOS devices.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2025
- **Updated:** 23 Jan 2025
- **Also known as:** GHSA-cfxg-rvg8-6h6c

## What is CVE-2025-23051?

CVE-2025-23051 is a high-severity code injection vulnerability in Hewlett Packard Enterprise (HPE) HPE Aruba Networking AOS, published on 14 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An authenticated parameter injection vulnerability exists in the web-based management interface of the AOS-8 and AOS-10 Operating Systems. Successful exploitation could allow an authenticated user to leverage parameter injection to overwrite arbitrary system files.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-23051 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23051 is a high-severity code injection vulnerability in Hewlett Packard Enterprise (HPE) HPE Aruba Networking AOS, published on 14 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23051 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise (HPE) HPE Aruba Networking AOS. 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-23051/ (Markdown: https://insights.sbomify.com/CVE-2025-23051/index.md)
```

## Sources

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

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