# CVE-2024-40119: Cross-site request forgery in n/a

> Remote attackers can change the admin password via CSRF, leading to account takeover on Nepstech WiFi routers.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-mpjf-jjj3-xgm7

## What is CVE-2024-40119?

CVE-2024-40119 is a high-severity vulnerability in n/a, published on 17 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Nepstech Wifi Router xpon (terminal) model NTPL-Xpon1GFEVN v.1.0 Firmware V2.0.1 contains a Cross-Site Request Forgery (CSRF) vulnerability in the password change function, which allows remote attackers to change the admin password without the user's consent, leading to a potential account takeover.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2024-40119 being exploited?

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

Public exploit code:

- Cross-Site Request Forgery (CSRF) vulnerability in the password  change function, which allows remote attackers to change the admin  password without the user's consent, leading to a potential account  takeover. (github_poc): https://github.com/baroi-ai/nepstech-xpon-router-CVE-2024-40119

## Fix prompt for AI coding agents

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

What it is: CVE-2024-40119 is a high-severity vulnerability in n/a, published on 17 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-40119 exists.

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-40119/ (Markdown: https://insights.sbomify.com/CVE-2024-40119/index.md)
```

## Sources

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

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