ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-11890

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.

Published Nov 4, 2025 · catalog updated Apr 8, 2026 · Crypto Payment Gateway with Payeer for WooCommerce

Last checked Oct 27, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-11890. EPSS is 0.30%. Act only if a listed version of Crypto Payment Gateway with Payeer for WooCommerce is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.30%
Remediation
Vendor / distro source
Affected products
vendor beycanpress Crypto Payment Gateway with Payeer for WooCommerce 0 ≤1.0.3

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor beycanpress Crypto Payment Gateway with Payeer for WooCommerce 0 ≤1.0.30 ≤1.0.3

How to fix CVE-2025-11890

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-11890. EPSS is 0.30%. Act only if a listed version of Crypto Payment Gateway with Payeer for WooCommerce is installed.

Which versions are affected?

Compare what you have installed with beycanpress Crypto Payment Gateway with Payeer for WooCommerce 0 ≤1.0.3 0 ≤1.0.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.30%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

WordPress security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Nov 4, 2025 · EUVD

    Detected

    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

  2. Apr 8, 2026 · EUVD

    Updated

    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

Sources

  • CVE.orgVulnerability recordCVE-2025-11890

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-11890

    30-day exploitation probability 0.30%

    first.org
  • EUVDVulnerability recordEUVD-2025-37590

    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-

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Oct 27, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 27, 2026
  • CVE.orgOct 24, 2026
  • EUVDOct 24, 2026