dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-15513

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 Float Payment Gateway plugin for WordPress is vulnerable to unauthorized modification of data due to improper error handling in the verifyFloatResponse() function in all versions up to, and including, 1.1.9. This makes it possible for unauthenticated attackers to mark any WooCommerce order as failed.

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 · moderate confidence

The Float Payment Gateway plugin for WordPress contains improper error handling in the verifyFloatResponse() function. This vulnerability allows unauthenticated attackers to manipulate the payment verification process and incorrectly mark WooCommerce orders as failed, disrupting the order lifecycle and potentially causing financial and operational issues.

MitigationUpdate the Float Payment Gateway plugin to version 1.1.10 or later which addresses the improper error handling. Alternatively, restrict access to the payment callback endpoint via firewall rules or IP allowlisting while awaiting the patch.

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 Float Payment Gateway plugin is installed
    In WordPress admin, go to Plugins > Instored Plugins and look for 'Float Payment Gateway' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'float-payment-gateway' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin Plugins list, click on the plugin to view details, or check the plugin's main PHP file header for the 'Version' comment. Compare this version against the patched version 1.1.10.
    Affected if The installed version is lower than 1.1.10 or the version cannot be determined
  3. Confirm WooCommerce is active with Float as payment method
    Go to WooCommerce > Settings > Payments in WordPress admin. Check if 'Float Payment Gateway' appears in the list of available payment methods and is enabled.
    Affected if WooCommerce is active and Float Payment Gateway is enabled as a payment method
  4. Determine if payment callback endpoint is exposed
    Check if the WordPress site responds to the payment callback URL (typically /?wc-api=wc_float_gateway or /?float_callback=1). Test this endpoint accessibility from an unauthenticated request using curl or browser.
    Affected if The callback endpoint is accessible without authentication and returns a response indicating the payment verification function is active

If the Float Payment Gateway plugin is installed, running a version before the patched release, and is enabled in WooCommerce with an exposed callback endpoint, the environment is likely affected by this improper error handling 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

Update the Float Payment Gateway plugin to version 1.1.10 or later which addresses the improper error handling. Alternatively, restrict access to the payment callback endpoint via firewall rules or IP allowlisting while awaiting the patch.

Recommended fix Moderate confidence

Latest version of Float Payment Gateway plugin (version > 1.1.9)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Float Payment Gateway' plugin
  4. Check if an update is available (version should be higher than 1.1.9)
  5. If an update is available, click 'Update Now' to install the latest version
  6. After updating, verify that orders can no longer be arbitrarily marked as failed by unauthenticated users

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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