dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-11771

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-21
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 (Token), Launchpad (Presale), ICO & IDO, Airdrop by TokenICO plugin for WordPress is vulnerable to unauthenticated and unauthorized modification of data due to missing authentication and capability checks on the 'createSaleRecord' function in all versions up to, and including, 2.4.7. This makes it possible for unauthenticated attackers to manipulate presales counters.

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 TokenICO WordPress plugin has a missing authorization vulnerability in the 'createSaleRecord' function through version 2.4.7. This function, intended to record presale transactions, lacks both authentication verification and capability checks, allowing any unauthenticated user to make arbitrary API calls that modify presale counter data.

MitigationUpdate the TokenICO plugin to version 2.4.8 or later which implements proper authentication and capability verification on the affected function. Until patched, consider disabling the plugin or restricting access via web server-level controls.

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 TokenICO plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'TokenICO' in the list of active plugins.
    Affected if TokenICO plugin appears in the installed plugins list
  2. Check installed TokenICO version
    In WordPress admin, go to Plugins > Installed Plugins. Find TokenICO and note the version number displayed below the plugin name. Compare against the affected range (versions through 2.4.7).
    Affected if The installed version is 2.4.7 or earlier
  3. Inspect the createSaleRecord function access
    Locate the plugin files via FTP or file manager (typically at wp-content/plugins/tokenico/). Examine the PHP file containing the 'createSaleRecord' function and verify if it registers a REST API endpoint or action hook without any authentication or capability checks.
    Affected if The createSaleRecord function is hooked to a public-facing action or REST route without require_auth, permission_callback, or capability checks such as 'manage_options'
  4. Test unauthenticated access to the vulnerable endpoint
    Using a tool like curl or Burp Suite, send a POST request to the suspected endpoint (commonly /wp-json/tokenico/v1/sale or similar REST routes) without providing any authentication tokens. Check if the request is processed without a 401 or 403 response.
    Affected if The request completes without authentication and modifies presale counter data in the database

A user is affected if the TokenICO plugin version is 2.4.7 or earlier and the createSaleRecord function is accessible 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the TokenICO plugin to version 2.4.8 or later which implements proper authentication and capability verification on the affected function. Until patched, consider disabling the plugin or restricting access via web server-level controls.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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