dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-2415

HIGH · 7.8 CVSS v3.1 Published 2024-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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
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'.

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 · high confidence

A command injection vulnerability exists in the Movistar 4G router (ES_WLD71-T1_v2.0.201820) where an authenticated attacker can execute arbitrary commands on the underlying operating system via the '/cgi-bin/gui.cgi' endpoint through a specially crafted POST request. This allows privilege escalation from authenticated user to full command execution on the device.

MitigationApply the vendor-supplied firmware patch when available; in the interim, restrict network access to the router's management interface to trusted IP addresses only and disable remote management if not required.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 router model
    Check the device label or web interface for the model number ES_WLD71-T1 (Movistar 4G router)
    Affected if The device is a Movistar 4G router model ES_WLD71-T1
  2. Check the firmware version
    Access the router web interface or check system information page for firmware version v2.0.201820
    Affected if The firmware version is v2.0.201820 or earlier (no patch version indicated)
  3. Verify web management interface accessibility
    Attempt to access the router's HTTP/HTTPS web interface from the network. Check if port 80 or 443 is listening on the device.
    Affected if The web management interface is reachable from untrusted networks
  4. Confirm the vulnerable CGI endpoint exists
    Check if /cgi-bin/gui.cgi endpoint responds on the device by making a GET request
    Affected if The /cgi-bin/gui.cgi endpoint is present and accessible
  5. Assess authentication exposure
    Review whether default credentials are in use, or if the web interface is accessible without VPN/tunnel from untrusted networks
    Affected if The router web interface uses default credentials or is accessible to untrusted users

You are affected if you have a Movistar 4G router (ES_WLD71-T1) running firmware v2.0.201820 with the web interface and /cgi-bin/gui.cgi endpoint accessible to untrusted users or using default credentials.

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

Apply the vendor-supplied firmware patch when available; in the interim, restrict network access to the router's management interface to trusted IP addresses only and disable remote management if not required.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,790
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2415 — 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-2415 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