dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-9149

HIGH · 8.6 CVSS v3.1 Published 2025-03-04
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 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Wind Media E-Commerce Website Template allows SQL Injection. This issue affects E-Commerce Website Template: before v1.5.

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

SQL Injection vulnerability in Wind Media E-Commerce Website Template (versions before v1.5) allows attackers to inject malicious SQL commands through unsanitized user inputs, potentially exposing or manipulating the database.

MitigationUpgrade to v1.5 or later to obtain vendor patch. Until then, implement parameterized queries/prepared statements and validate all user inputs to prevent SQL injection 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
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 the installed version of Wind Media E-Commerce Website Template
    Check for a version file (often named version.php, version.txt, or about.php in the root or admin directory), look at the footer/admin panel for version info, or search source files for a version string like 'v1.x'
    Affected if The version displayed is below v1.5 (e.g., v1.0, v1.1, v1.2, v1.3, v1.4)
  2. Locate code that processes user input in SQL queries
    Search source files (.php) for SQL keywords (SELECT, INSERT, UPDATE, DELETE) combined with superglobal variables ($_GET, $_POST, $_REQUEST) or input functions without visible sanitization
    Affected if User-supplied input from forms, URL parameters, or cookies is directly concatenated into SQL query strings without using prepared statements or parameter binding
  3. Inspect database interaction functions for unsanitized parameters
    Review functions that execute queries (mysqli_query, mysql_query, PDO::query) and verify whether the arguments contain raw user input or only use whitelisted/validated values
    Affected if The application passes unsanitized $_POST, $_GET, or $_REQUEST values directly into query execution functions
  4. Test common input fields for potential SQL injection points
    Identify login, search, filter, or form submission fields; review the corresponding PHP handlers to see if inputs are used in queries without escaping or prepared statements
    Affected if User input fields in login, search, category filters, or contact forms feed directly into SQL without escaping functions like mysqli_real_escape_string, parameterized queries, or input validation

You are affected if your Wind Media E-Commerce Website Template is version v1.4 or earlier AND your installation contains PHP files that pass user input directly into SQL queries without using prepared statements or escaping functions.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to v1.5 or later to obtain vendor patch. Until then, implement parameterized queries/prepared statements and validate all user inputs to prevent SQL injection attacks.

Recommended fix Moderate confidence

v1.5

  1. Obtain the Wind Media E-Commerce Website Template version 1.5 from the official vendor or your licensing source
  2. Backup your current website files and database before performing any upgrade
  3. Replace all template files with the version 1.5 files
  4. Verify that the SQL injection vulnerability is resolved by testing input fields that could be exploited
  5. Ensure all other functionality works correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

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-9149 — 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-9149 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