dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-9243

HIGH · 8.1 CVSS v3.1 Published 2025-10-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
The Cost Calculator Builder plugin for WordPress is vulnerable to unauthorizedmodification of data due to a missing capability check on the get_cc_orders and update_order_status functions in all versions up to, and including, 3.5.32. This makes it possible for authenticated attackers, with Subscriber-level access and above, to access order management functions and modify order status.

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 · high confidence

The Cost Calculator Builder WordPress plugin lacks proper capability checks on the get_cc_orders and update_order_status functions, allowing any authenticated user with Subscriber-level access or higher to invoke these order management functions and modify order statuses. This is a broken access control vulnerability where the plugin trusts user authentication without verifying authorization level.

MitigationUpdate the plugin to version 3.5.33 or later which contains the capability check fix. If immediate update is not possible, restrict user registration or audit all user accounts to prevent exploitation by low-privilege attackers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Cost Calculator Builder plugin version
    Navigate to WordPress Admin > Plugins, locate Cost Calculator Builder, and note the installed version number. Alternatively, check the plugin's main PHP file for the version constant or header.
    Affected if The installed version is lower than 3.5.33 (e.g., 3.5.32, 3.5.30, etc.)
  2. Locate the vulnerable plugin file containing order functions
    In the wp-content/plugins/cost-calculator-builder directory, search for files containing 'get_cc_orders' or 'update_order_status' function definitions. These are typically in the includes or core plugin files.
    Affected if The plugin file with these functions exists and is active on the site
  3. Verify if capability checks exist in the vulnerable functions
    Open the file containing get_cc_orders and update_order_status functions. Search for capability checks such as 'current_user_can' with appropriate permissions (e.g., 'manage_options', 'edit_orders') before executing the function logic.
    Affected if No capability check (like current_user_can('manage_options')) is found before the order retrieval or status update logic in either function
  4. Confirm the site allows subscriber-level user access
    Check WordPress user roles: go to Users > All Users and verify if any users exist with the Subscriber role. Alternatively, confirm the site permits user registration with Subscriber-level access.
    Affected if Any authenticated user with Subscriber role or higher can access the site (which is the default WordPress configuration)

The environment is affected if the Cost Calculator Builder plugin version is below 3.5.33 and the get_cc_orders/update_order_status functions lack proper capability validation (e.g., current_user_can checks), allowing any authenticated subscriber-level user to manipulate orders.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 3.5.33 or later which contains the capability check fix. If immediate update is not possible, restrict user registration or audit all user accounts to prevent exploitation by low-privilege attackers.

Recommended fix High confidence

Cost Calculator Builder version 3.5.33 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Cost Calculator Builder' plugin
  4. Click 'Update now' if an update is available, or manually update to version 3.5.33 or later
  5. Verify the plugin updated successfully by checking the version number

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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