# CVE-2024-40495: Code injection in n/a

> Authenticated attackers can execute arbitrary code on Linksys E2500 routers via the parental control unblock function.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/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:** 24 Jul 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-6ggw-rwr9-p77h

## What is CVE-2024-40495?

CVE-2024-40495 is a high-severity code injection vulnerability in n/a, published on 24 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was discovered in Linksys Router E2500 with firmware 2.0.00, allows authenticated attackers to execute arbitrary code via the hnd_parentalctrl_unblock function.

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

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

It affects 1 product.


Products: Linksys E2500 Firmware.

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

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

## Is CVE-2024-40495 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-44654](https://insights.sbomify.com/CVE-2025-44654/): Path traversal in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-40495 is a high-severity code injection vulnerability in n/a, published on 24 Jul 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-40495 in the wild and no public exploit code.

Affected product: n/a. 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-40495/ (Markdown: https://insights.sbomify.com/CVE-2024-40495/index.md)
```

## Sources

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

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