dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-2128

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 time-based SQL Injection via the ‘order_ids’ parameter in all versions up to, and including, 3.2.67 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 (versions up to 3.2.67) contains a time-based SQL Injection vulnerability in the 'order_ids' parameter. The flaw stems from insufficient input escaping combined with lack of prepared statements in the underlying SQL query, allowing authenticated users with Subscriber-level access to inject arbitrary SQL commands.

MitigationUpgrade to version 3.2.68 or later, which contains the security fix. If immediate patching is not possible, restrict the 'order_ids' parameter through web application firewall rules or temporarily disable affected functionality until the patch can be applied.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Confirm Cost Calculator Builder plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Cost Calculator Builder' in the list, or check the plugin files in wp-content/plugins/cost-calculator-builder/ for a version file or header
    Affected if The plugin is present on the WordPress site
  2. Determine the installed plugin version
    In WordPress admin, click on the plugin to view its details and note the version number displayed, or open the main plugin PHP file and look for the 'Version' header comment
    Affected if The installed version is 3.2.67 or lower (versions prior to 3.2.68)
  3. Verify user role access exists
    In WordPress admin, go to Users > All Users and check if any users have the 'Subscriber' role assigned, or check if the vulnerable endpoint is accessible to authenticated users with subscriber-level permissions
    Affected if Subscriber-level or higher user accounts exist on the site and can access the plugin functionality
  4. Identify if the order_ids parameter is in use
    Review web server access logs for requests to the plugin's endpoints containing 'order_ids' parameter, or check the plugin's ajax/admin-ajax handlers for code that processes the order_ids parameter
    Affected if Requests to the plugin handling the order_ids parameter are possible or have been made

The site is affected if the Cost Calculator Builder plugin version is 3.2.67 or lower AND subscriber-level user accounts can access functionality that uses the order_ids parameter.

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

Upgrade to version 3.2.68 or later, which contains the security fix. If immediate patching is not possible, restrict the 'order_ids' parameter through web application firewall rules or temporarily disable affected functionality until the patch can be applied.

Recommended fix Moderate confidence

3.2.68 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Cost Calculator Builder' plugin
  4. Check the current version is 3.2.67 or below
  5. Click 'Update Now' if an update is available, or manually upload version 3.2.68 or higher from wordpress.org/plugins/cost-calculator-builder
  6. Verify the update completed successfully
  7. Test that the Cost Calculator Builder functionality works as expected

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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