CVE-2025-14757 MEDIUM

CVE-2025-14757: Cost Calculator Builder <= 3.6.9 - Missing Authorization to Unauthenticated Payment Status Bypass

Vendor Stylemix
Product Cost Calculator Builder
Weakness CWE-862 · Missing authorization
Published January 16, 2026
Last update April 8, 2026

CVSS base score

5.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality None
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

The Cost Calculator Builder plugin for WordPress is vulnerable to Unauthenticated Payment Status Bypass in all versions up to, and including, 3.6.9 only when used in combination with Cost Calculator Builder PRO. This is due to the complete_payment AJAX action being registered via wp_ajax_nopriv, making it accessible to unauthenticated users, and the complete() function only verifying a nonce without checking user capabilities or order ownership. Since nonces are exposed to all visitors via window.ccb_nonces in the page source, any unauthenticated attacker can mark any order's payment status as "completed" without actual payment.

Explanation of Vulnerability in Simple Terms

02Summary

Cost Calculator Builder through version 3.6.9 lacks proper authorization checks, allowing unauthenticated attackers to modify data via network requests. The vulnerability does not expose sensitive information or disrupt service availability, but permits unauthorized changes to calculator configurations or stored data. Site administrators should update to a version newer than 3.6.9 as soon as available.

What an attacker can do

03Attacker Capabilities

Modify calculator data or settings without authentication.

Potential impact on your site

04Site Impact

Attackers can alter calculator configurations, pricing rules, or stored form data without logging in.

Conditions required to exploit

05Prerequisites

Network access only; no authentication or user interaction required.

Key dates

06Disclosure timeline

January 16, 2026 CVE published
April 8, 2026 Record updated