NP Quote Request for WooCommerce <= 1.9.179 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Disclosure
Strategic Overview
- Status
- Patched in 1.9.180
- Affected Plugin
- NP Quote Request for WooCommerce
- Affected Version
<= 1.9.179- CVSS
- 7.5High
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-13558
At a glance
CVE-2024-13558 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the NP Quote Request for WooCommerce WordPress plugin, affecting versions <= 1.9.179. 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 1.9.180; sites on affected versions should update now. Disclosed March 2025, reported by Tim Coen.
Vulnerability Overview
The NP Quote Request for WooCommerce plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.9.179 due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to read the content of quote requests.
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
Reaching this weakness in NP Quote Request for WooCommerce <= 1.9.179 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 NP Quote Request for WooCommerce the fix is 1.9.180: builds <= 1.9.179 are affected, anything from 1.9.180 onward is not.
Remediation
Update to version 1.9.180, 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: NP Quote Request for WooCommerce 1.9.180 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C