# CVE-2024-2415: Command injection vulnerability in Movistar 4G router

> An authenticated attacker can execute arbitrary commands on the Movistar 4G router via a crafted POST request.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Mar 2024
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jcpj-8g57-23q8

## What is CVE-2024-2415?

CVE-2024-2415 is a high-severity command injection vulnerability in Router Movistar 4G, published on 13 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Command injection vulnerability in Movistar 4G router affecting version ES_WLD71-T1_v2.0.201820. This vulnerability allows an authenticated user to execute commands inside the router by making a POST request to the URL '/cgi-bin/gui.cgi'.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2024-2415?


## How do I fix CVE-2024-2415?

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

## Is CVE-2024-2415 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2415 and fix it if it is affected.

What it is: CVE-2024-2415 is a high-severity command injection vulnerability in Router Movistar 4G, published on 13 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-2415 in the wild and no public exploit code.

Affected product: Router Movistar 4G. 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-2024-2415/ (Markdown: https://insights.sbomify.com/CVE-2024-2415/index.md)
```

## Sources

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

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