dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-39209

MEDIUM · 6.3 CVSS v3.1 Published 2024-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
luci-app-sms-tool v1.9-6 was discovered to contain a command injection vulnerability via the score parameter.

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

luci-app-sms-tool v1-6 contains a command injection vulnerability where the score parameter is not properly sanitized before being used in a system call, allowing an attacker to execute arbitrary shell commands.

MitigationImplement strict input validation on the score parameter using an allowlist approach, and refactor code to avoid passing user input directly to system commands or use parameterized execution methods.

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

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

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 luci-app-sms-tool version
    On the OpenWrt device, run 'opkg list-installed | grep luci-app-sms-tool' or check /usr/lib/luci/cbi.lua for the version string, or inspect the opkg info output
    Affected if The installed version is 1-6 or lower (any version from v1 through v1-6)
  2. Locate the sms-tool CGI or API endpoint
    Search for the application files in /www/cgi-bin/ or /usr/lib/lua/luci/ for files containing 'sms' or 'score', or list installed luci-app-sms-tool files with 'opkg files luci-app-sms-tool'
    Affected if The application is installed and the score parameter handler exists in the codebase
  3. Inspect the score parameter handling code
    Examine the source code of the CGI/script handling the score parameter - look for system(), popen(), or exec() calls where the score parameter is concatenated directly into the command string without sanitization
    Affected if The code shows direct concatenation of the score parameter into a shell command without input validation or escaping
  4. Verify the feature is exposed via HTTP interface
    Check if the Luci web interface exposes the sms-tool application with score functionality, typically at /cgi-bin/luci or a specific API endpoint; confirm the parameter is accepted via GET or POST request
    Affected if The score parameter can be submitted through the web interface and reaches the vulnerable code path

You are affected if luci-app-sms-tool version 1-6 or lower is installed and the score parameter feature is accessible through the web interface, with the vulnerable code path present in the application.

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 strict input validation on the score parameter using an allowlist approach, and refactor code to avoid passing user input directly to system commands or use parameterized execution methods.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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