dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-12150

CRITICAL · 9.8 CVSS v3.1 Published 2025-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 →
100/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 Eron Software Wowwo CRM allows Blind SQL Injection. This issue affects Wowwo CRM.  NOTE: The vendor did not inform about the completion of the fixing process within the specified time. The CVE will be updated when new information becomes available.

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

A blind SQL injection vulnerability exists in Wowwo CRM where user-supplied input is not properly sanitized before being used in SQL queries. This allows remote attackers to inject malicious SQL code and potentially extract sensitive data from the database or perform unauthorized operations. The 'blind' classification means the attacker infers information through behavioral differences rather than seeing direct output.

MitigationSince the vendor has not yet released a complete patch, immediate mitigations include deploying a WAF with SQL injection rules, implementing strict input validation at a proxy layer, and restricting database account privileges to minimum required operations. The application should be isolated from direct internet exposure until a vendor fix is available.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Wowwo CRM is deployed
    Identify if the target system is running Wowwo CRM by checking application metadata, headers, or footprinting the web application's structure and identifying CRM-specific endpoints
    Affected if The system is running Wowwo CRM without a vendor-supplied patch for CVE-2024-12150
  2. Identify user input entry points
    Map all locations where user-supplied data enters the application, including form fields, query parameters, headers, and API inputs, particularly in search, filter, or login functionalities
    Affected if User input is accepted without centralized sanitization controls
  3. Locate SQL query implementations
    Review application source code or configuration to find where SQL queries are constructed, focusing on dynamic query building that incorporates user-supplied parameters
    Affected if SQL queries are built using string concatenation or unsanitized parameter interpolation with user input
  4. Verify lack of input sanitization
    Inspect the code paths between user input fields and SQL execution points to confirm no parameterized queries, prepared statements, or input validation/sanitization functions are applied
    Affected if User input flows directly into SQL queries without sanitization, prepared statements, or parameterized queries
  5. Review database access controls
    Examine the database user account used by the application to determine if it operates with elevated privileges beyond what the CRM functionality requires
    Affected if The application database account has privileges beyond SELECT/INSERT/UPDATE/DELETE on CRM-specific tables

The environment is affected if Wowwo CRM is running and user-supplied input is used in SQL queries without sanitization or parameterized query protection.

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

Since the vendor has not yet released a complete patch, immediate mitigations include deploying a WAF with SQL injection rules, implementing strict input validation at a proxy layer, and restricting database account privileges to minimum required operations. The application should be isolated from direct internet exposure until a vendor fix is available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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