CVE-2026-0656
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 iPaymu Payment Gateway for WooCommerce plugin for WordPress is vulnerable to Missing Authentication in all versions up to, and including, 2.0.2 via the 'check_ipaymu_response' function. This is due to the plugin not validating webhook request authenticity through signature verification or origin checks. This makes it possible for unauthenticated attackers to mark WooCommerce orders as paid by sending crafted POST requests to the webhook endpoint without any payment occurring, as well as enumerate order IDs and obtain valid order keys via GET requests, exposing customer order PII including names, addresses, and purchased products.
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 iPaymu Payment Gateway plugin for WooCommerce fails to authenticate webhook requests in its check_ipaymu_response function, allowing unauthenticated attackers to send POST requests that falsely mark orders as paid without any actual payment. Additionally, GET requests to the same endpoint expose customer PII by enumerating order IDs and revealing order keys.
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
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the iPaymu plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'ipaymu' or similar, and identify the main plugin file to determine the installed versionAffected if The plugin folder exists and contains the iPaymu Payment Gateway for WooCommerce plugin files
-
Identify the plugin versionOpen the main plugin PHP file (usually ipaymu.php or similar) and look for the version comment or header that specifies the plugin version numberAffected if The installed version falls within any affected version range for this CVE (check against official iPaymu plugin changelog for vulnerable versions)
-
Verify the check_ipaymu_response function existsSearch the plugin source code for the 'check_ipaymu_response' function and examine its implementation for missing authentication checksAffected if The function exists and processes webhook requests without validating cryptographic signatures or verifying request origin
-
Test webhook endpoint authenticationSend a crafted POST request to the plugin's webhook endpoint (typically the WordPress callback URL for iPaymu) with fake payment data, observe if order status changes without actual payment processingAffected if Orders can be marked as paid via unauthenticated POST requests to the webhook endpoint
-
Test PII exposure via GET requestsSend GET requests to the webhook endpoint with different order ID parameters, check if order details including customer PII and order keys are returned without authenticationAffected if GET requests to the endpoint expose customer personal information or order keys by simply varying the order ID parameter
A user is affected if the iPaymu Payment Gateway plugin is installed with a vulnerable version that lacks signature verification on its webhook endpoint, allowing unauthenticated POST requests to modify order status or GET requests to expose customer PII.
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 dataImplement cryptographic signature verification for all webhook requests and validate the origin/referrer to ensure requests come from iPaymu's servers before processing any order status changes or returning order data.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0656 — 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-2026-0656 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