CVE-2025-11890
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 · uneditedThe 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.
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 confidenceThe Crypto Payment Gateway with Payeer plugin for WooCommerce fails to perform server-side validation of payment status at the /wc-api/bp-payeer-gateway-callback endpoint, allowing unauthenticated attackers to manipulate order statuses from unpaid to paid without actual payment being received.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the Payeer plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Crypto Payment Gateway with Payeer' or 'bp-payeer-gateway' in the listAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionClick on the plugin in the WordPress plugins list to view its version number, or check the plugin's main PHP file header for the 'Version' tagAffected if Version is at or below the last known vulnerable version (compare against current version on WordPress.org or the vendor's release notes)
-
Verify the callback endpoint is accessibleMake a GET or POST request to your site's /wc-api/bp-payeer-gateway-callback endpoint using curl or a browser. For example: curl -I https://yourdomain.com/wc-api/bp-payeer-gateway-callbackAffected if The endpoint returns a 200 OK response rather than a 404, indicating the plugin route is registered and active
-
Check if order status can be modified without payment validationReview the plugin source code, specifically the callback handler for bp-payeer-gateway-callback. Look for server-side calls to the Payeer API to verify payment status before updating order statusAffected if The callback handler updates order status without performing remote API validation against Payeer's servers
-
Review server access logs for suspicious callback requestsCheck web server logs (Apache/Nginx) for POST requests to /wc-api/bp-payeer-gateway-callback with unusual parameters, especially those resulting in order status changes to 'completed' or 'processing'Affected if There are callback requests that changed order statuses without corresponding payment verification logs
You are affected if the Crypto Payment Gateway with Payeer plugin is installed and its callback endpoint accepts status updates without performing server-side validation against the Payeer API.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version when available, and implement server-side verification of payment status against the Payeer API before updating any order status.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11890 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11890 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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