WP Scraper <= 5.7 - Missing Authorization to Arbitrary Page/Post Creation
Strategic Overview
- Status
- Patched in 5.8
- Affected Plugin
- WP Scraper
- Affected Version
<= 5.7- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-3663
At a glance
CVE-2024-3663 is a medium-severity Missing Authorization vulnerability in the WP Scraper WordPress plugin, affecting versions <= 5.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 5.8; sites on affected versions should update now. Disclosed May 2024, reported by Lucio Sá.
Vulnerability Overview
The WP Scraper plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the wp_scraper_multi_scrape_action() function in all versions up to, and including, 5.7. This makes it possible for authenticated attackers, with subscriber-level access and above, to create arbitrary pages and posts.
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 interaction from a victim user.
CWE-862: Missing Authorization
WP Scraper <= 5.7 carries this weakness at wp_scraper_multi_scrape_action(), and reaching it takes a caller who can reach the endpoint. 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 WP Scraper the fix is 5.8: builds <= 5.7 are affected, anything from 5.8 onward is not.
Remediation
Update to version 5.8, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Scraper 5.8 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