dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14460

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-07
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 Piraeus Bank WooCommerce Payment Gateway plugin for WordPress is vulnerable to unauthorized order status modification in all versions up to, and including, 3.1.4. This is due to missing authorization checks on the payment callback endpoint handler when processing the 'fail' callback from the payment gateway. This makes it possible for unauthenticated attackers to change any order's status to 'failed' via the publicly accessible WooCommerce API endpoint by providing only the order ID (MerchantReference parameter), which can be easily enumerated as order IDs are sequential integers. This can cause significant business disruption including canceled shipments, inventory issues, and 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 confidence

The Piraeus Bank WooCommerce Payment Gateway plugin lacks authorization validation on its payment callback endpoint. Attackers can send a 'fail' callback with just a sequential order ID (MerchantReference) to change any order's status to 'failed' without authentication, causing business disruption.

MitigationAdd server-side authorization validation (e.g., signature verification, token validation, or IP allowlisting) to the payment callback endpoint to ensure only legitimate gateway requests can modify order statuses.

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 Piraeus Bank WooCommerce plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Piraeus Bank WooCommerce Payment Gateway' or check wp-content/plugins/ for a directory containing 'piraeus' or 'piraeus-bank'
    Affected if The plugin is installed and active
  2. Check plugin version
    In WordPress admin plugin list, note the version number displayed for Piraeus Bank WooCommerce Payment Gateway. Compare against any official changelogs or security releases
    Affected if Version is prior to any patched release (if known) or cannot be determined
  3. Verify callback endpoint is exposed
    Check if the payment callback URL is publicly accessible. Common patterns: /?wc-api=wc_piraeus_gateway&action=callback or /wc-api/piraeus/callback. Attempt a HEAD request to these endpoints without authentication
    Affected if Endpoint responds with HTTP 200 and accepts requests without authentication
  4. Inspect plugin for authorization checks
    Review the plugin's callback handler file (typically in includes/class-wc-piraeus-gateway.php or similar) and look for validation of MerchantReference, signature verification, or token checks before processing status changes
    Affected if No authorization, signature, or token validation code is found before order status modification
  5. Test order status modification capability
    Using a non-authenticated request, send a callback with a valid but arbitrary order ID and action=fail (or similar parameter). Check if the order status changes to 'failed' without valid credentials
    Affected if Order status changes to failed without providing valid authentication credentials or gateway signature

If the Piraeus Bank WooCommerce Payment Gateway plugin is active and its callback endpoint processes status changes without requiring authentication tokens, signatures, or IP validation, the environment is affected by this vulnerability.

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

Add server-side authorization validation (e.g., signature verification, token validation, or IP allowlisting) to the payment callback endpoint to ensure only legitimate gateway requests can modify order statuses.

Recommended fix Moderate confidence

Version 3.1.5 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Piraeus Bank WooCommerce Payment Gateway' plugin
  4. Click 'Update now' if an update is available, or manually download version 3.1.5 or later from the WordPress plugin repository
  5. After updating, verify the new version number reflects 3.1.5 or higher in the Plugins list

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14460 — 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-14460 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