dbcve.org
Sparkle Demo ImporterWordPress extension · Wpneuron

CVE-2024-6120

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-22
Fix available
A fix is available. Upgrade to 1.4.8 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Sparkle Demo Importer WordPress plugin lacks proper capability checks on multiple functions that handle database reset and demo plugin installation. Any authenticated user with Subscriber-level access can execute these administrative functions, allowing mass deletion of content and installation of demo plugins.

MitigationAdd WordPress capability checks (e.g., current_user_can('manage_options') or 'administrator' role verification) to all functions handling database reset and plugin installation, restricting these actions to administrator-level users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sparkle Demo ImporterWordPress extension
Affected:< 1.4.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Sparkle Demo Importer plugin is installed
    Check WordPress plugin directory for 'sparkle-demo-importer' folder, or view installed plugins in WordPress admin under Plugins > Installed Plugins, or run: wp plugin list --name='sparkle-demo-importer'
    Affected if Plugin is present in the WordPress installation
  2. Check installed plugin version
    Open the main plugin file (sparkle-demo-importer.php) and look for the Version header in the plugin comments, or check via WordPress admin plugin list, or run: wp plugin get sparkle-demo-importer --field=version
    Affected if Version number is less than 1.4.8
  3. Identify Subscriber-level users
    In WordPress admin under Users > All Users, look for any users with Subscriber role, or run: wp user list --role=subscriber --field=user_login,roles
    Affected if At least one user with Subscriber role exists in the system
  4. Confirm plugin handles database reset or demo installation
    Review plugin source code for functions named 'reset', 'database', 'import', 'install_plugin', or similar demo installation routines; check for AJAX actions handling these operations in the plugin's main file or includes folder
    Affected if Plugin contains database reset or demo plugin installation functions without capability checks
  5. Verify low-privilege access to admin functions
    Attempt to access plugin admin functions while logged in as a Subscriber-level user (e.g., call wp_ajax_sparkle_reset_database or similar action), or inspect code for missing current_user_can() calls before sensitive operations
    Affected if Subscriber-level users can trigger database reset or plugin installation functions without proper authorization checks

Environment is affected if Sparkle Demo Importer plugin version is below 1.4.8 AND at least one Subscriber-level user exists who could potentially access the vulnerable database reset or demo installation functions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.4.8 or later
Fixed in 1.4.8
Interim mitigation

Add WordPress capability checks (e.g., current_user_can('manage_options') or 'administrator' role verification) to all functions handling database reset and plugin installation, restricting these actions to administrator-level users only.

Recommended fix High confidence

Sparkle Demo Importer version 1.4.8

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Sparkle Demo Importer in the plugin list
  4. Click Update Now to update to version 1.4.8 or later
  5. Verify the plugin version shows 1.4.8 or higher after update
  6. Confirm the update was successful

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sparkle Demo Importer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6120 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6120 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data