InPost for WooCommerce <= 1.4.0 and InPost PL <= 1.4.4 - Missing Authorization to Unauthenticated Arbitrary File Read and Delete
Strategic Overview
- Status
- Patched in 1.4.5
- Affected Plugin
- InPost PL
- Affected Version
<= 1.4.4- CVSS
- 10.0Critical
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-6500
At a glance
CVE-2024-6500 is a critical-severity Missing Authorization vulnerability in the InPost PL WordPress plugin, affecting versions <= 1.4.4. It carries a CVSS score of 10.0 (reachable over the network; low attack complexity; high confidentiality, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.4.5; sites on affected versions should update now. Disclosed August 2024, reported by 1337_Wannabe.
Vulnerability Overview
The InPost for WooCommerce plugin and InPost PL plugin for WordPress are vulnerable to unauthorized access and deletion of data due to a missing capability check on the 'parse_request' function in all versions up to, and including, 1.4.0 (for InPost for WooCommerce) as well as 1.4.4 (for InPost PL). This makes it possible for unauthenticated attackers to read and delete arbitrary files on Windows servers. On Linux servers, only files within the WordPress install will be deleted, but all files can be read.
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, availability.
CWE-862: Missing Authorization
InPost PL <= 1.4.4 carries this weakness at parse_request, and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For InPost PL the fix is 1.4.5: builds <= 1.4.4 are affected, anything from 1.4.5 onward is not.
Remediation
Update to version 1.4.5, 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: InPost PL 1.4.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C