dbcve.org
Cost Calculator BuilderWordPress extension · Stylemixthemes

CVE-2024-43144

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to 3.2.16 or later.
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 StylemixThemes Cost Calculator Builder allows SQL Injection.This issue affects Cost Calculator Builder: from n/a through 3.2.15.

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 SQL injection vulnerability exists in StylemixThemes Cost Calculator Builder plugin up to version 3.2.15. The vulnerability stems from improper neutralization of special elements in SQL commands, allowing attackers to inject malicious SQL queries through unspecified input vectors in the calculator builder functionality.

MitigationUpdate Cost Calculator Builder to the latest version beyond 3.2.15 once a patched release is available. If immediate patching is not possible, restrict access to affected calculator endpoints and implement input validation 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.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cost Calculator BuilderWordPress extension
Affected:< 3.2.16

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. Verify Cost Calculator Builder plugin is installed
    Locate the plugin in your WordPress installation under wp-content/plugins and confirm the 'cost-calculator-builder' directory exists, or check via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin directory 'cost-calculator-builder' is present in the plugins folder
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Cost Calculator Builder and view the version number displayed, or inspect the main plugin file header for the Version field
    Affected if The version number is 3.2.15 or lower
  3. Confirm calculator builder functionality is active
    Check if any calculator has been created and published by visiting the frontend of your site or reviewing calculator entries in the WordPress admin dashboard under the Cost Calculator menu
    Affected if At least one calculator is active or has been built using the builder
  4. Inspect calculator builder endpoints
    Review your web server logs or WAF logs for requests to paths containing 'cost-calculator' or 'calculator-builder' with unusual SQL-like patterns such as UNION, SELECT, or WHERE in query parameters
    Affected if Unfiltered SQL syntax appears in requests to calculator-related URLs
  5. Check for unauthorized database changes
    Review your MySQL database tables, particularly any tables prefixed with 'ccb_' or custom calculator tables, for unexpected entries or signs of SQL injection payloads
    Affected if Foreign SQL payloads or unauthorized modifications are found in calculator-related database tables

You are affected if the Cost Calculator Builder plugin version is 3.2.15 or lower and the calculator builder functionality is active on your site.

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
Upgrade available Upgrade to 3.2.16 or later
Fixed in 3.2.16
Interim mitigation

Update Cost Calculator Builder to the latest version beyond 3.2.15 once a patched release is available. If immediate patching is not possible, restrict access to affected calculator endpoints and implement input validation at the web application firewall level.

Recommended fix High confidence

3.2.16

  1. 1. Back up your WordPress site (database and files) before updating
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find 'Cost Calculator Builder' by StylemixThemes in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.2.16
  5. 5. Alternatively, download version 3.2.16 from the WordPress plugin repository or StylemixThemes website
  6. 6. If manually updating: deactivate the current plugin, delete it, then upload and activate version 3.2.16
  7. 7. After updating, clear any caching plugins and test the calculator functionality to ensure it works correctly

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

Fix this in Cost Calculator Builder Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,170
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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