WooCommerce Square <= 5.1.1 - Unauthenticated Insecure Direct Object Reference to Sensitive Information Exposure in get_token_by_id
Strategic Overview
- Status
- Patched in 4.2.3
- Affected Plugin
- WooCommerce Square
- Affected Version
4.2.0 – < 5.1.2 · 10 branches- CVSS
- 7.5High
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2025-13457
At a glance
CVE-2025-13457 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the WooCommerce Square WordPress plugin, affecting versions 4.2.0 – < 5.1.2 · 10 branches. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 4.2.3; sites on affected versions should update now. Disclosed January 2026, reported by DityaRA.
Vulnerability Overview
The WooCommerce Square plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.1.1 via the get_token_by_id function due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to expose arbitrary Square "ccof" (credit card on file) values and leverage this value to potentially make fraudulent charges on the target site.
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. A successful exploit has high impact on confidentiality.
CWE-639: Authorization Bypass Through User-Controlled Key
WooCommerce Square 4.2.0 – < 5.1.2 · 10 branches carries this weakness at ccof, and reaching it takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For WooCommerce Square the fix is 4.2.3: builds 4.2.0 – < 5.1.2 · 10 branches are affected, anything from 4.2.3 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 4.2.3, 4.3.2, 4.4.2, 4.5.2, 4.6.4, 4.7.4, 4.8.8, 4.9.9, 5.0.1, 5.1.2
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: WooCommerce Square 4.2.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C