# CVE-2025-11073: Keyfactor RG-EW5100BE HTTP POST Request cmd command injection

> Remote attackers can execute arbitrary commands on Keyfactor RG-EW5100BE routers via the HTTP POST request handler.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2025
- **Updated:** 29 Sep 2025
- **Also known as:** GHSA-5gp6-hwm5-6f8j

## What is CVE-2025-11073?

CVE-2025-11073 is a medium-severity command injection vulnerability in Keyfactor RG-EW5100BE, published on 27 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was detected in Keyfactor RG-EW5100BE EW_3.0B11P280_EW5100BE-PRO_12183019. The affected element is an unknown function of the file /cgi-bin/luci/api/cmd of the component HTTP POST Request Handler. The manipulation of the argument url results in command injection. The attack can be launched remotely. The exploit is now public and may be used.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2025-11073 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11073 is a medium-severity command injection vulnerability in Keyfactor RG-EW5100BE, published on 27 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11073 in the wild and no public exploit code.

Affected product: Keyfactor RG-EW5100BE. 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-11073/ (Markdown: https://insights.sbomify.com/CVE-2025-11073/index.md)
```

## Sources

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

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