Sparkle Demo Importer <= 1.4.7 - Missing Authorization to Authorized(Subscriber+) Post/Pages/Attachements Deletion and Demo Data Import
Strategic Overview
- Status
- Patched in 1.4.8
- Affected Plugin
- Sparkle Demo Importer
- Affected Version
<= 1.4.7- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-6120
At a glance
CVE-2024-6120 is a medium-severity Missing Authorization vulnerability in the Sparkle Demo Importer WordPress plugin, affecting versions <= 1.4.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.4.8; sites on affected versions should update now. Disclosed June 2024, reported by Lucio Sá.
Vulnerability Overview
The Sparkle Demo Importer plugin for WordPress is vulnerable to unauthorized database reset and demo data import due to a missing capability check on the multiple functions in all versions up to and including 1.4.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete all posts, pages, and uploaded files, as well as download and install a limited set of demo plugins.
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. A successful exploit has high impact on integrity.
CWE-862: Missing Authorization
Reaching this weakness in Sparkle Demo Importer <= 1.4.7 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 Sparkle Demo Importer the fix is 1.4.8: builds <= 1.4.7 are affected, anything from 1.4.8 onward is not.
Remediation
Update to version 1.4.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: Sparkle Demo Importer 1.4.8 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