Skip to main content
Vulnerability Database/CVE-2025-11773

CVE-2025-11773: TokenICO WordPress Plugin Auth Bypass

CVE-2025-11773 is an authentication bypass flaw in the TokenICO WordPress plugin that lets authenticated attackers modify smart contract addresses. This article covers technical details, affected versions, and steps to secure your site.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-11773 Overview

CVE-2025-11773 affects the Cryptocurrency (Token), Launchpad (Presale), ICO & IDO, Airdrop by TokenICO plugin for WordPress. The flaw stems from a missing capability check on the saveDeployedContract function in all versions up to and including 2.4.7. Authenticated attackers with Subscriber-level access or higher can overwrite the tokenico_deployed_contracts WordPress option. This allows them to poison the smart contract addresses displayed to visitors. The weakness is tracked under [CWE-862: Missing Authorization].

Critical Impact

Low-privileged WordPress users can replace legitimate smart contract addresses with attacker-controlled addresses, redirecting cryptocurrency transactions from site visitors to wallets controlled by the attacker.

Affected Products

  • TokenICO Cryptocurrency Token Launchpad plugin for WordPress, versions ≤ 2.4.7
  • WordPress sites running the vulnerable plugin with Subscriber registration enabled
  • Any ICO, IDO, presale, or airdrop site relying on the plugin to display contract addresses

Discovery Timeline

  • 2025-11-21 - CVE-2025-11773 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-11773

Vulnerability Analysis

The TokenICO plugin exposes a REST API route that invokes the saveDeployedContract handler. The handler updates the tokenico_deployed_contracts WordPress option, which stores the list of deployed smart contract addresses rendered on front-end pages. The handler does not perform a current_user_can() capability check before writing the option. Any authenticated session, including Subscriber accounts created through standard WordPress registration, can issue the request and overwrite the stored data.

The practical impact is specific to cryptocurrency sites. Visitors who copy the displayed contract address to interact with a token presale or airdrop will send funds to the attacker-supplied address. The vulnerability does not grant direct code execution or data exfiltration, but it enables high-value financial fraud through content integrity loss.

Root Cause

The root cause is a missing authorization check in the REST API callback registered for the saveDeployedContract operation. The plugin relies on a permission callback that returns true for any authenticated user instead of restricting access to administrators. Reviewers can confirm the pattern in the plugin source at the WordPress Plugin RestAPI Code reference.

Attack Vector

Exploitation requires network access to the WordPress REST API and valid credentials for any role at Subscriber level or above. The attacker authenticates, obtains a REST nonce, and sends a request to the vulnerable endpoint with a crafted payload containing attacker-controlled contract addresses. The server persists the data in the wp_options table, and the poisoned addresses render on the next page load. No user interaction is required beyond the attacker's own session.

No verified public exploit code is available. See the Wordfence Vulnerability Report and the WordPress Changeset History for additional technical context.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2025-11773

Indicators of Compromise

  • Unexpected values in the tokenico_deployed_contracts row of the wp_options table, especially addresses that do not match the site owner's deployed contracts.
  • Access log entries showing POST or PUT requests to REST API routes under /wp-json/ that reference TokenICO endpoints from low-privileged accounts.
  • Recent Subscriber or Contributor account creations followed by REST API calls to the plugin.

Detection Strategies

  • Compare the current tokenico_deployed_contracts option value against a known-good baseline stored outside the WordPress database.
  • Alert on authenticated REST API calls to the TokenICO plugin routes originating from non-administrator users.
  • Review database audit logs for update_option events targeting the tokenico_deployed_contracts key.

Monitoring Recommendations

  • Enable WordPress REST API request logging and forward it to a central analytics platform for correlation with user role data.
  • Monitor on-chain traffic to the published contract addresses and alert when the public-facing value diverges from the canonical deployment.
  • Track creation of new low-privileged accounts followed by option-write activity within a short time window.

How to Mitigate CVE-2025-11773

Immediate Actions Required

  • Update the TokenICO plugin to a version later than 2.4.7 as soon as the vendor publishes a patched release.
  • Audit the current value of tokenico_deployed_contracts and restore legitimate addresses if tampering is detected.
  • Temporarily disable public user registration or restrict the Subscriber role until the plugin is patched.

Patch Information

The vulnerability affects all versions through 2.4.7. Administrators should monitor the WordPress Changeset History and the Wordfence Vulnerability Report for a fixed release that introduces a proper current_user_can() capability check on the saveDeployedContract handler.

Workarounds

  • Deactivate the TokenICO plugin until a patched release is installed if the site cannot tolerate the risk.
  • Use a web application firewall rule to block REST API requests to the TokenICO routes from any user that is not an administrator.
  • Enforce strong registration controls, including CAPTCHA and email verification, to limit automated creation of Subscriber accounts.
bash
# Example WordPress CLI check for tampering of the stored option
wp option get tokenico_deployed_contracts --format=json

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.