CVE-2025-14755 stylemix CVE debrief

Who should care

Defenders responsible for WordPress installations using the Cost Calculator Builder plugin, especially those using the plugin in combination with Cost Calculator Builder PRO, should assess exposure and prioritize updates to mitigate potential price manipulation attacks.

Why it matters

The Cost Calculator Builder plugin for WordPress has an unauthenticated price manipulation vulnerability when used with Cost Calculator Builder PRO. Defenders should prioritize verifying and updating the plugin to mitigate potential price manipulation attacks. The vulnerability allows attackers to add products to a cart with controlled prices due to insufficient authorization checks. This requires verification of plugin version and exposure, as well as prioritization of updates to mitigate the vulnerability.

• Potential price manipulation by unauthenticated attackers.
• Possible addition of products to cart with controlled prices.
• Need for verification of plugin version and exposure.
• Prioritization of updates to mitigate vulnerability.

Technical summary

The Cost Calculator Builder plugin for WordPress is vulnerable to unauthenticated price manipulation and Insecure Direct Object Reference (IDOR) when used with Cost Calculator Builder PRO. The ccb_woocommerce_payment AJAX action is registered via wp_ajax_nopriv, making it accessible to unauthenticated users. The renderWooCommercePayment() function passes user-controlled data directly to CCBWooCheckout::init() without authorization checks.

Defensive priority

Defenders should prioritize verifying and updating the plugin to mitigate potential price manipulation attacks.

Recommended defensive actions

• Verify and update the Cost Calculator Builder plugin to the latest version.
• Restrict access to the ccb_woocommerce_payment AJAX action.
• Monitor for suspicious activity related to price manipulation.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The vulnerability exists in the ccb_woocommerce_payment AJAX action, which is accessible to unauthenticated users. The renderWooCommercePayment() function passes user-controlled data directly to CCBWooCheckout::init() without authorization checks.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.