dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-11986

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

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 Crypto plugin for WordPress is vulnerable to Information exposure in all versions up to, and including, 2.22. This is due to the plugin registering an unauthenticated AJAX action (wp_ajax_nopriv_crypto_connect_ajax_process) that allows calling the register and savenft methods with only a publicly-available nonce check and no wallet signature verification. This makes it possible for unauthenticated attackers to set a site-wide global authentication state via a single transient, bypassing all access controls for ALL visitors to the site. The impact is complete bypass of [crypto-block] shortcode restrictions and page-level access controls, affecting all site visitors for one hour, plus the ability to inject arbitrary data into the plugin's custom_users table.

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 WordPress Crypto plugin registers an unauthenticated AJAX action (wp_ajax_nopriv_crypto_connect_ajax_process) that accepts register and savenft method calls relying only on a publicly-available nonce without wallet signature verification. This allows unauthenticated attackers to set a site-wide global authentication state via a transient, bypassing all [crypto-block] shortcode restrictions and page-level access controls for all visitors for one hour, plus inject arbitrary data into the plugin's custom_users table.

MitigationUpgrade to the latest version of the Crypto plugin which implements proper wallet signature verification and restricts the AJAX endpoints. Until patched, consider disabling the plugin or adding firewall rules to block the vulnerable AJAX endpoints.

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. Verify Crypto plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate the Crypto plugin. Note the version number. Compare against the patched version provided in plugin release notes.
    Affected if Crypto plugin is installed and active, and version is older than the patched release that adds wallet signature verification.
  2. Confirm vulnerable AJAX endpoint is registered
    Check if the action wp_ajax_nopriv_crypto_connect_ajax_process is active by inspecting source code in wp-content/plugins/crypto/ajax-handler.php or similar, or by testing unauthenticated access to /wp-admin/admin-ajax.php?action=crypto_connect_ajax_process
    Affected if The AJAX endpoint responds to unauthenticated requests without requiring wallet signature verification.
  3. Inspect plugin custom_users table for unauthorized entries
    Query the WordPress database: SELECT * FROM wp_custom_users (or similar table name used by plugin) WHERE user_address or user_wallet is set to unknown/attackers wallet addresses, or created_at falls outside expected activity periods.
    Affected if Table contains unexpected user records, particularly those with unusual wallet addresses or timestamps indicating automated creation.
  4. Check for suspicious authentication transients
    Query WordPress transients: SELECT * FROM wp_options WHERE option_name LIKE '%transient%crypto%' OR option_name LIKE '%_transient%crypto%'. Look for transients setting global authentication states that persist for visitors.
    Affected if Global authentication transients exist that grant site-wide access without proper wallet verification, particularly any set unexpectedly.

A user is affected if the WordPress Crypto plugin is installed with a version lacking wallet signature verification, the vulnerable unauthenticated AJAX endpoint is accessible, or unauthorized entries appear in the custom_users table or transients.

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 the latest version of the Crypto plugin which implements proper wallet signature verification and restricts the AJAX endpoints. Until patched, consider disabling the plugin or adding firewall rules to block the vulnerable AJAX endpoints.

Recommended fix High confidence

Crypto plugin version 2.23 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Crypto plugin
  4. Check if an update is available and update to version 2.23 or later
  5. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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