Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11771: CWE-306 Missing Authentication for Critical Function in beycanpress Cryptocurrency (Token), Launchpad (Presale), ICO & IDO, Airdrop by TokenICO

0
Medium
VulnerabilityCVE-2025-11771cvecve-2025-11771cwe-306
Published: Fri Nov 21 2025 (11/21/2025, 07:31:55 UTC)
Source: CVE Database V5
Vendor/Project: beycanpress
Product: Cryptocurrency (Token), Launchpad (Presale), ICO & IDO, Airdrop by TokenICO

Description

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.6. This makes it possible for unauthenticated attackers to manipulate presales counters.

AI-Powered Analysis

AILast updated: 11/21/2025, 08:34:07 UTC

Technical Analysis

CVE-2025-11771 identifies a vulnerability in the beycanpress WordPress plugin designed for managing cryptocurrency token sales, including presales, ICOs, IDOs, and airdrops. The core issue is a missing authentication and capability check in the 'createSaleRecord' function, which is responsible for recording presale transactions. Because this function lacks proper access control, any unauthenticated user can invoke it to alter presale counters arbitrarily. This unauthorized modification can distort the actual number of tokens sold or available, potentially misleading investors, disrupting fundraising efforts, and damaging the credibility of the token issuer. The vulnerability affects all versions up to and including 2.4.6 of the plugin. The CVSS 3.1 base score is 5.3 (medium severity), reflecting that the attack vector is network-based, requires no privileges or user interaction, and impacts integrity but not confidentiality or availability. No patches or official fixes have been published as of now, and no exploits have been observed in the wild. The vulnerability falls under CWE-306, which concerns missing authentication for critical functions, a common issue in web applications that can lead to unauthorized data manipulation. Given the plugin’s role in financial transactions related to cryptocurrency, the integrity impact is significant despite the medium CVSS score. Organizations relying on this plugin should be aware of the risk of presale data tampering and take immediate steps to mitigate exposure.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to the integrity of cryptocurrency fundraising activities. Manipulation of presale counters can lead to inaccurate reporting of token sales, potentially causing financial losses, regulatory scrutiny, and reputational damage. Since the plugin is used in ICOs, IDOs, and airdrops, unauthorized changes could disrupt token distribution schedules and investor trust. Although confidentiality and availability are not directly affected, the integrity compromise could indirectly impact business operations and compliance with financial regulations. European financial regulators emphasize transparency and accuracy in fundraising, so manipulated presale data could trigger audits or sanctions. Organizations operating in the cryptocurrency sector or using WordPress-based launchpads should consider this vulnerability a significant operational risk. The lack of authentication also means attackers can exploit this remotely without credentials, increasing the threat surface. The absence of known exploits provides a window for proactive mitigation, but the potential for future exploitation remains high.

Mitigation Recommendations

1. Immediately restrict access to the vulnerable plugin’s functionality by implementing web application firewall (WAF) rules that block unauthenticated requests to the 'createSaleRecord' endpoint or related AJAX actions. 2. Disable or deactivate the beycanpress plugin if it is not essential or if presale activities are not currently active. 3. Monitor presale counters and related data for anomalies or unexpected changes, using logging and alerting mechanisms to detect unauthorized modifications. 4. Implement custom authentication and capability checks at the web server or application level as a temporary control until an official patch is released. 5. Regularly back up presale data to enable restoration in case of tampering. 6. Engage with the plugin vendor or community to obtain updates or patches as soon as they become available. 7. Educate staff responsible for managing ICOs and token sales about the vulnerability and the importance of verifying presale data integrity. 8. Consider deploying intrusion detection systems (IDS) tuned to detect unusual traffic patterns targeting the plugin’s endpoints. 9. Review and harden WordPress security configurations, including limiting plugin installation to trusted sources and minimizing plugin usage to reduce attack surface.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-14T23:33:33.261Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69202359cf2d47c38997b415

Added to database: 11/21/2025, 8:31:21 AM

Last enriched: 11/21/2025, 8:34:07 AM

Last updated: 11/22/2025, 6:29:01 AM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats