dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-40119

HIGH · 8.8 CVSS v3.1 Published 2024-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Nepstech Wifi Router NTPL-Xpon1GFEVN v.1.0 firmware V2.0.1 contains a CSRF vulnerability in its password change function. Attackers can trick authenticated administrators into unknowingly submitting malicious password change requests, allowing unauthorized modification of the admin password and potential account takeover.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations including password change; add SameSite cookie attributes and validate Origin/Referer headers to prevent cross-site request forgery attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model and firmware version
    Access the router web interface or use commands like `cat /proc/version`, `nvram show`, or check admin/status pages to retrieve the exact model number and firmware version (e.g., NTPL-Xpon1GFEVN v.1.0 firmware V2.0.1)
    Affected if The device is Nepstech Wifi Router NTPL-Xpon1GFEVN v.1.0 with firmware V2.0.1 or earlier versions of this firmware line
  2. Confirm the web management interface is enabled
    Access the router admin login page (typically at http://<router-ip>/ or http://<router-ip>/cgi-bin/webproc) and verify the interface is reachable
    Affected if The web management interface is exposed and accessible (even if requiring authentication)
  3. Inspect password change request for CSRF tokens
    Log into the admin panel, navigate to the password change function, use browser developer tools to inspect the HTTP request (Network tab) when submitting a new password; examine the request headers and body for anti-CSRF tokens (e.g., token, csrf, nonce parameters)
    Affected if The password change POST request lacks anti-CSRF tokens or unique session tokens in the request parameters
  4. Check SameSite cookie attributes on session cookies
    In browser developer tools, inspect cookies set by the router (Application/Storage tab) after login; look for SameSite attribute on session cookies
    Affected if Session cookies lack SameSite attribute or have SameSite set to None/Lax without Secure flag
  5. Verify Origin/Referer header validation
    Send a crafted password change request from an external host with manipulated Origin/Referer headers (using curl or similar) and observe if the request is rejected or accepted
    Affected if The router accepts password change requests regardless of Origin/Referer header values (no validation performed)

You are affected if you are running Nepstech Wifi Router NTPL-Xpon1GFEVN v.1.0 firmware V2.0.1 (or earlier) with the web management interface enabled and the password change function lacks CSRF protection mechanisms (anti-CSRF tokens, SameSite cookies, or Origin/Referer validation).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations including password change; add SameSite cookie attributes and validate Origin/Referer headers to prevent cross-site request forgery attacks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-40119 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-40119 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data