CVE-2024-6010 json
Cost Calculator Builder PRO <= 3.2.1 - Unauthenticated Price Manipulation
published 2y ago modified 4mo ago also EUVD-2024-47174
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
The 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.
Is CVE-2024-6010 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- StylemixThemes Cost Calculator Builder PRO
- stylemixthemes cost_calculator_builder_pro
Classification
- Weakness
-
- CWE-472 External Control of Assumed-Immutable Web Parameter
- Technology feeds
References
-
wordfence.com
/threat-intel/vulnerabilities/id/fc04e676-e394-488e-a239-95af5f865613?source=cve
third-party-advisory
-
plugins.trac.wordpress.org
/browser/cost-calculator-builder/trunk/frontend/dist/order.js
issue-tracking
- docs.stylemixthemes.com /cost-calculator-builder/changelog-1/changelog-pro-version
- plugins.trac.wordpress.org /changeset/3172590/
Sources
- CVE List CVE-2024-6010
- NVD CVE-2024-6010
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.