dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12392

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-18
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

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 Cryptocurrency Payment Gateway for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'handle_optin_optout' function in all versions up to, and including, 2.0.25. This makes it possible for unauthenticated attackers to opt in and out of tracking.

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 Cryptocurrency Payment Gateway for WooCommerce WordPress plugin versions up to 2.0.25 lacks proper authorization checks on the handle_optin_optout function, allowing unauthenticated users to arbitrarily modify tracking opt-in/opt-out settings via the vulnerable endpoint.

MitigationUpdate the plugin to version 2.0.26 or later which includes proper capability validation. Alternatively, implement a capability check (e.g., manage_options) on the handle_optin_optout function to restrict access to administrators only.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Verify the plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Cryptocurrency Payment Gateway for WooCommerce' in the installed plugins list
    Affected if the plugin appears in the installed plugins list
  2. Check the installed plugin version
    Click on the plugin in the WordPress plugins list to view its details, or inspect the plugin header in wp-content/plugins/cryptocurrency-payment-gateway-for-woocommerce/cryptocurrency-payment-gateway.php for the 'Version' field
    Affected if the version number is 2.0.25 or lower (any version up to and including 2.0.25)
  3. Confirm the vulnerable function exists
    Access the WordPress site files and locate the handle_optin_optout function in the plugin code, typically in the main plugin file or includes folder
    Affected if the handle_optin_optout function exists in the plugin code without a capability check (such as 'manage_options' or 'administrator')
  4. Test endpoint accessibility
    Send a crafted request to the endpoint handling optin_optout actions (commonly via wp-admin/admin-ajax.php or a dedicated API endpoint) without providing authentication credentials
    Affected if the request succeeds and modifies tracking settings without returning an authorization error

A user is affected if the Cryptocurrency Payment Gateway for WooCommerce plugin version is 2.0.25 or lower and the handle_optin_optout function can be accessed or modified without authentication.

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 2.0.26 or later which includes proper capability validation. Alternatively, implement a capability check (e.g., manage_options) on the handle_optin_optout function to restrict access to administrators only.

Recommended fix High confidence

Version 2.0.26 or later of Cryptocurrency Payment Gateway for WooCommerce

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Cryptocurrency Payment Gateway for WooCommerce' in the plugin list
  4. Check the current version number displayed under the plugin name
  5. If the installed version is 2.0.25 or earlier, click 'Update Now' to upgrade to the latest version
  6. Alternatively, download version 2.0.26 or later from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the new version number confirms 2.0.26 or higher is installed

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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