dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-10865

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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 Sensitive Information Exposure in all versions up to, and including, 4.0.11 via the (template body). This makes it possible for unauthenticated attackers to extract the plaintext Stripe secret key, Razorpay secret key, and PayPal client_secret embedded in the page source of any page containing a calculator, enabling full control of the merchant's payment gateway accounts. This exposure only occurs when the 'use in all calculators' option is enabled for one or more payment gateways in the plugin's global settings.

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 plugin for WordPress embeds payment gateway secret keys (Stripe, Razorpay, PayPal) in plaintext within the HTML source of pages containing calculators when the 'use in all calculators' global setting is enabled. Unauthenticated attackers can view page source to extract these credentials and gain full control of the merchant's payment accounts.

MitigationUpdate the plugin to version 4.0.12 or later. Also rotate all exposed payment gateway credentials (Stripe secret key, Razorpay secret key, PayPal client_secret) immediately, as they may have been compromised.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 > Plugins and verify 'Cost Calculator Builder' appears in the installed plugins list
    Affected if plugin is not installed means not affected by this specific vulnerability
  2. Check installed plugin version
    In WordPress admin > Plugins > Cost Calculator Builder, view the version number displayed beneath the plugin name; compare against the fixed version 4.0.12
    Affected if version is below 4.0.12 indicates the plugin may contain this vulnerability
  3. Verify 'use in all calculators' global setting is enabled
    Navigate to the plugin settings panel (usually under 'Cost Calculator' menu in WP admin) and locate the 'use in all calculators' or global settings option; check whether it is toggled ON or enabled
    Affected if this global setting is enabled means credentials could be exposed in calculator HTML
  4. Inspect HTML source of public calculator pages for plaintext secrets
    Visit any published calculator page in a browser, right-click and select 'View Page Source', then search for strings containing 'sk_live', 'rzp_live', 'secret', or 'client_secret' within script or input tags
    Affected if Stripe secret key (sk_live...), Razorpay key, or PayPal client_secret appears in plaintext in the HTML source indicates active exploitation

User is affected if the Cost Calculator Builder plugin version is below 4.0.12 AND the 'use in all calculators' global setting is enabled, with plaintext payment credentials visible in calculator page source code

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 4.0.12 or later. Also rotate all exposed payment gateway credentials (Stripe secret key, Razorpay secret key, PayPal client_secret) immediately, as they may have been compromised.

Recommended fix High confidence

Cost Calculator Builder version 4.0.12 or later

  1. Update the Cost Calculator Builder plugin to version 4.0.12 or later via WordPress plugin management
  2. After updating, inspect the page source of a page containing a calculator to confirm sensitive keys (Stripe secret key, Razorpay secret key, PayPal client_secret) are no longer visible in plaintext
  3. As a precautionary measure, rotate any API keys that may have been exposed (Stripe secret key, Razorpay secret key, PayPal client_secret)

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
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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