dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-15475

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The PayHere Payment Gateway Plugin for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to an improper validation logic in the check_payhere_response function in all versions up to, and including, 2.3.9. This makes it possible for unauthenticated attackers to change the status of pending WooCommerce orders to paid/completed/on hold.

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 confidence

The PayHere Payment Gateway Plugin for WooCommerce has improper validation in its check_payhere_response callback function, allowing unauthenticated attackers to spoof payment confirmation responses. This enables attackers to manipulate the callback to mark pending WooCommerce orders as paid, completed, or on hold without actually making any payment.

MitigationUpdate to plugin version 2.3.10 or later which contains the security fix. If no update is available, implement webhook signature verification and merchant ID validation in the check_payhere_response function before processing any order status changes.

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify PayHere plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'PayHere Payment Gateway for WooCommerce' or check the plugins directory for payhere-woocommerce folder
    Affected if plugin is installed and active
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, click on the PayHere plugin details, and note the version number. Compare against the fixed version 2.3.10
    Affected if installed version is lower than 2.3.10
  3. Inspect the check_payhere_response function
    Access the plugin source file (typically in wp-content/plugins/payhere-woocommerce/includes/class-payhere-response.php or similar) and locate the check_payhere_response callback function
    Affected if function exists and lacks signature verification or merchant ID validation
  4. Verify callback accessibility
    Check if the callback endpoint is publicly accessible (typically at ?wc-api=check_payhere_response or similar webhook URL) by reviewing WordPress rewrite rules or the plugin's endpoint registration
    Affected if callback endpoint is reachable without authentication
  5. Check for validation logic
    Review the check_payhere_response function code for presence of: (1) merchant ID validation against configured value, (2) signature/mac verification using shared secret, (3) verification against PayHere API
    Affected if no merchant ID validation and no signature verification logic is present in the callback handler

User is affected if the PayHere Payment Gateway for WooCommerce plugin is installed with a version lower than 2.3.10 and the check_payhere_response callback lacks proper validation mechanisms.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to plugin version 2.3.10 or later which contains the security fix. If no update is available, implement webhook signature verification and merchant ID validation in the check_payhere_response function before processing any order status changes.

Recommended fix Moderate confidence

Any version above 2.3.9 (latest available version recommended)

  1. Navigate to WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the PayHere Payment Gateway Plugin for WooCommerce
  4. Check if the current version is 2.3.9 or below
  5. If vulnerable, click Update Now to install the latest version
  6. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the order status modification functionality works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15475 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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