Cost Calculator BuilderWordPress extension · Stylemixthemes
CVE-2024-6010
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 · uneditedThe Cost Calculator Builder PRO plugin for WordPress is vulnerable to price manipulation in all versions up to, and including, 3.2.1. This is due to the plugin allowing the price field to be manipulated prior to processing via the 'create_cc_order' function, called from the Cost Calculator Builder plugin. This makes it possible for unauthenticated attackers to manipulate the price of orders submitted via the calculator. Note: this vulnerability was partially patched with the release of Cost Calculator Builder version 3.2.17.
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 confidenceThe Cost Calculator Builder PRO plugin for WordPress fails to validate price values server-side before processing orders through the 'create_cc_order' function. Unauthenticated attackers can manipulate the price parameter in their requests to set arbitrary prices, bypassing client-side calculations entirely. This is a classic business logic flaw where user-supplied input is trusted for financial transactions.
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
<= 3.1.96CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installation and versionNavigate to WordPress admin dashboard > Plugins, locate 'Cost Calculator Builder' (or 'Cost Calculator Builder PRO'), and check the installed version number against the affected range (<= 3.1.96)Affected if The plugin version is 3.1.96 or lower, or if the version cannot be determined but the plugin is present
-
Verify the create_cc_order endpoint is accessibleInspect the plugin files (typically in /wp-content/plugins/cost-calculator-builder/) for the 'create_cc_order' function definition and determine if it is hooked to a REST API route or AJAX action that handles order creation without authenticationAffected if The create_cc_order function is hooked to a publicly accessible action (such as wp_ajax_nopriv_ or wp_ajax_ hook) without requiring authentication
-
Inspect server-side price validation logicLocate the create_cc_order function in the plugin source code and examine whether it performs server-side validation of the 'price' or 'total' parameter before processing the order, looking for any price calculation from fixed formulas or verification against stored valuesAffected if The function accepts and uses a price parameter directly from the request without recalculating or validating it against fixed formula values
-
Check order processing configurationReview the plugin settings in WordPress admin under the Cost Calculator Builder settings panel to see if order processing to payment gateways is enabled and whether custom price submission is allowedAffected if Order processing is enabled and the plugin accepts user-supplied price values in the order creation flow
A user is affected if they have Cost Calculator Builder PRO version 3.1.96 or lower installed with the create_cc_order function accessible without authentication and no server-side price validation present.
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement server-side price validation by calculating totals from fixed formulas rather than accepting user-supplied prices, and add cryptographic validation or server-side lookups to verify order amounts before processing.
Cost Calculator Builder PRO version 3.2.17 or later (latest available version)
- 1. Backup your WordPress site and database before making any changes
- 2. Navigate to Plugins > Installed Plugins in WordPress admin
- 3. Find 'Cost Calculator Builder' (or 'Cost Calculator Builder PRO') in the plugin list
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. After updating, verify that the calculator forms still function correctly by submitting a test order
- 6. Confirm the 'create_cc_order' function now properly validates price values server-side
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cost Calculator Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6010 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6010 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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