dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-11939

HIGH · 7.5 CVSS v3.1 Published 2025-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The Cost Calculator Builder PRO plugin for WordPress is vulnerable to blind time-based SQL Injection via the ‘data’ parameter in all versions up to, and including, 3.2.15 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

The Cost Calculator Builder PRO WordPress plugin fails to properly escape the 'data' parameter and lacks prepared statements in its SQL queries, allowing unauthenticated attackers to inject arbitrary SQL commands. The vulnerability is a blind time-based SQL injection, meaning attackers infer information from response time differences rather than seeing direct database output.

MitigationUpdate the Cost Calculator Builder PRO plugin to version 3.2.15 or later. If immediate updating is not possible, consider restricting access to the affected endpoint at the web application firewall level.

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

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

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. Verify Cost Calculator Builder PRO is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the cost-calculator-builder-pro folder, or query the wp_options table for the active_plugins entry.
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin is listed in WordPress active plugins.
  2. Determine installed plugin version
    Open the main plugin file (cost-calculator-builder-pro.php) and locate the Version header in the plugin comments, or check the Version field in the WordPress plugins admin page.
    Affected if The version is lower than 3.2.15 (the fixed version).
  3. Confirm the vulnerable endpoint is accessible
    Identify the WordPress REST API endpoint or PHP file that handles the 'data' parameter. Common paths include /wp-json/ccb/v1/ or direct AJAX handlers in the plugin's includes/ folder. Review access logs for requests to these endpoints.
    Affected if The plugin is active and the endpoint is reachable without authentication.
  4. Inspect the data parameter handling
    Examine the plugin source code in files that process the 'data' parameter. Look for direct SQL queries without $wpdb->prepare() or similar prepared statement usage.
    Affected if Code shows unsanitized use of the 'data' parameter in SQL queries.
  5. Check for time-based anomaly patterns in logs
    Review web server access logs and application logs for the affected endpoint. Look for repeated requests with unusual payload patterns in the 'data' parameter that could indicate injection testing, especially requests followed by consistent time delays.
    Affected if Log patterns show suspicious 'data' parameter values or abnormal response timing patterns.

A user is affected if the Cost Calculator Builder PRO plugin is installed, active, and the version is below 3.2.15 with the vulnerable endpoint exposed.

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

Update the Cost Calculator Builder PRO plugin to version 3.2.15 or later. If immediate updating is not possible, consider restricting access to the affected endpoint at the web application firewall level.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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