dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-15565

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-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 Nexi XPay plugin for WordPress is vulnerable to unauthorized modification of data due to missing authorization checks on the redirect function in all versions up to, and including, 8.3.0. This makes it possible for unauthenticated attackers to mark pending WooCommerce orders as paid/completed.

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 Nexi XPay plugin for WordPress is vulnerable to broken access control in its redirect function (versions up to 8.3.0). The function lacks proper authorization checks, allowing unauthenticated attackers to craft requests that mark pending WooCommerce orders as paid/completed. This enables attackers to falsely complete orders without legitimate payment.

MitigationUpdate the Nexi XPay plugin to version 8.3.1 or later, which includes proper authorization checks on the redirect function. If immediate update is not possible, implement server-side validation to verify that order status changes originate only from legitimate payment gateway callbacks.

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 Nexi XPay plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Nexi XPay' or 'xpay' in the plugin list
    Affected if The Nexi XPay plugin appears in the installed plugins list
  2. Check installed Nexi XPay version
    In WordPress admin, go to Plugins > Installed Plugins, find Nexi XPay, and note the version number displayed below the plugin name
    Affected if The installed version is lower than 8.3.1 (versions prior to 8.3.1 lack the authorization fix)
  3. Confirm WooCommerce is active
    In WordPress admin, go to Plugins > Installed Plugins and verify WooCommerce is installed and activated
    Affected if WooCommerce is active and the Nexi XPay plugin is installed (the vulnerability exploits WooCommerce order status handling)
  4. Test for unauthenticated order status modification
    Send a direct HTTP request to the Nexi XPay redirect/callback endpoint without providing authentication credentials, attempting to modify a pending order status
    Affected if The request succeeds and modifies order status without requiring authentication or authorization validation

The environment is affected if Nexi XPay plugin versions below 8.3.1 are installed with WooCommerce active, and the redirect function can be accessed and used to modify order statuses without authentication.

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 the Nexi XPay plugin to version 8.3.1 or later, which includes proper authorization checks on the redirect function. If immediate update is not possible, implement server-side validation to verify that order status changes originate only from legitimate payment gateway callbacks.

Recommended fix Moderate confidence

Latest version of Nexi XPay plugin (version > 8.3.0)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Nexi XPay plugin
  4. Check if an update is available and install the latest version
  5. Verify the updated version number is above 8.3.0
  6. Test that WooCommerce order status changes now require proper authorization

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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