CVE-2025-15513

Float Payment Gateway <= 1.1.9 - Improper Authorization to Unauthenticated Order Status Manipulation

2026-01-13 17:33

Strategic Overview

Status: Patched in 1.1.10
Affected Plugin: Float Payment Gateway
Affected Version: <= 1.1.9
CVSS: 5.3Medium
Weakness type: CWE-863 · Incorrect Authorization
CVE: CVE-2025-15513

View all Float Payment Gateway vulnerabilities

At a glance

CVE-2025-15513 is a medium-severity Incorrect Authorization vulnerability in the Float Payment Gateway WordPress plugin, affecting versions <= 1.1.9. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.10; sites on affected versions should update now. Disclosed January 2026, reported by Md. Moniruzzaman Prodhan (NomanProdhan).

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-863: Incorrect Authorization

Float Payment Gateway <= 1.1.9 carries this weakness at verifyFloatResponse(), and reaching it takes no account at all. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. For Float Payment Gateway the fix is 1.1.10: builds <= 1.1.9 are affected, anything from 1.1.10 onward is not.

Remediation

Update to version 1.1.10, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Float Payment Gateway 1.1.10 closes this, and updating the plugin is the step that ends it.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-15513 https://www.wordfence.com/threat-intel/vulnerabilities/id/b2c7fb39-d128-4285-8bc3-1e192e1e1196 https://nvd.nist.gov/vuln/detail/CVE-2025-15513

CVSS Vector

5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/