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-11890: CWE-862 Missing Authorization in beycanpress Crypto Payment Gateway with Payeer for WooCommerce

0
High
VulnerabilityCVE-2025-11890cvecve-2025-11890cwe-862
Published: Tue Nov 04 2025 (11/04/2025, 04:27:16 UTC)
Source: CVE Database V5
Vendor/Project: beycanpress
Product: Crypto Payment Gateway with Payeer for WooCommerce

Description

The Crypto Payment Gateway with Payeer for WooCommerce plugin for WordPress is vulnerable to payment bypass in all versions up to, and including, 1.0.3. This is due to the plugin not properly verifying a payments status through server-side validation though the /wc-api/bp-payeer-gateway-callback endpoint. This makes it possible for unauthenticated attackers to update unpaid order statuses to paid resulting in a loss of revenue.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 19:39:03 UTC

Technical Analysis

The vulnerability identified as CVE-2025-11890 affects the Crypto Payment Gateway with Payeer for WooCommerce plugin, a WordPress extension that facilitates cryptocurrency payments via the Payeer system. The root cause is a missing authorization check (CWE-862) in the plugin's server-side callback endpoint (/wc-api/bp-payeer-gateway-callback). This endpoint is responsible for updating order payment statuses based on payment confirmations. However, due to improper validation, unauthenticated attackers can send crafted requests to this endpoint to change the status of unpaid orders to paid without any legitimate payment verification. This bypasses the intended payment verification mechanism, allowing attackers to fraudulently mark orders as paid and potentially receive goods or services without payment. The vulnerability affects all versions up to and including 1.0.3. The CVSS v3.1 base score is 7.5, reflecting a high severity due to the vulnerability's network accessibility (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and impact limited to integrity (I:H) without affecting confidentiality or availability. No patches are currently linked, and no known exploits have been observed in the wild, but the flaw's nature makes it a significant risk for e-commerce merchants relying on this plugin for payment processing.

Potential Impact

The primary impact of this vulnerability is financial loss due to fraudulent order fulfillment. Attackers can manipulate order statuses to appear paid without actual payment, leading to revenue loss and potential inventory depletion. This undermines the integrity of the payment process and damages merchant trust. Additionally, the vulnerability could facilitate further fraud schemes, such as reselling goods obtained through unauthorized orders. For organizations, this can result in direct monetary losses, reputational damage, and increased operational costs related to fraud investigation and remediation. The vulnerability also exposes weaknesses in payment processing security, which could be exploited in combination with other attacks. Since the flaw requires no authentication or user interaction and is exploitable remotely, the attack surface is broad, affecting any WooCommerce store using the vulnerable plugin version. This can disrupt business operations and erode customer confidence in online payment security.

Mitigation Recommendations

Until an official patch is released, affected organizations should immediately disable the Crypto Payment Gateway with Payeer for WooCommerce plugin to prevent exploitation. Merchants should implement additional server-side validation for payment status updates, such as verifying payment confirmations directly with the Payeer API before marking orders as paid. Monitoring and alerting on unusual order status changes can help detect exploitation attempts early. Restricting access to the callback endpoint via IP whitelisting or web application firewall (WAF) rules can reduce exposure. Once a patch is available, promptly apply it and verify that authorization checks are correctly enforced. Additionally, merchants should review transaction logs regularly and reconcile payments to identify discrepancies. Educating staff about this vulnerability and encouraging vigilance in payment processing workflows will further reduce risk.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-16T19:01:24.095Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690984dc2b77ca42b4883e74

Added to database: 11/4/2025, 4:45:16 AM

Last enriched: 2/27/2026, 7:39:03 PM

Last updated: 3/24/2026, 1:38:09 AM

Views: 129

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 more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses