dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-8430

MEDIUM · 5.3 CVSS v3.1 Published 2024-10-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Spice Starter Sites plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the spice_starter_sites_importer_creater function in all versions up to, and including, 1.2.5. This makes it possible for unauthenticated attackers to import demo content.

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 Spice Starter Sites WordPress plugin lacks a capability check on the spice_starter_sites_importer_creater function, allowing unauthenticated attackers to invoke this function and import arbitrary demo content into the WordPress site. This authorization bypass affects all versions up to 1.2.5.

MitigationUpdate to version 1.2.6 or later which includes the missing capability check. If no update is available, manually add a capability check (e.g., current_user_can('manage_options')) to the spice_starter_sites_importer_creater function.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 Spice Starter Sites plugin is installed
    Check the WordPress plugin list under Plugins > Installed Plugins to confirm the Spice Starter Sites plugin is present and active
    Affected if The plugin is installed and active in WordPress
  2. Determine the installed plugin version
    View the plugin details in the WordPress admin panel or inspect the main plugin file (typically in wp-content/plugins/spice-starter-sites/) to find the version number in the plugin header comment
    Affected if The installed version is 1.2.5 or any earlier version (versions up to and including 1.2.5 are affected)
  3. Inspect the spice_starter_sites_importer_creater function
    Locate the plugin source files and examine the function named spice_starter_sites_importer_creater for the presence of a capability check (such as current_user_can()) at the function entry point
    Affected if The function exists but lacks any capability check (e.g., current_user_can('manage_options') or similar) before executing its import logic
  4. Check for unauthorized demo content imports
    Review the WordPress posts, pages, and media library for any recently created content that matches demo content from starter site templates, especially content created unexpectedly or without admin action
    Affected if Unexpected demo content posts, pages, or media files exist on the site that were not intentionally imported by an administrator

A user is affected if the Spice Starter Sites plugin version is 1.2.5 or earlier AND the spice_starter_sites_importer_creater function lacks a capability check, allowing unauthenticated content imports.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.2.6 or later which includes the missing capability check. If no update is available, manually add a capability check (e.g., current_user_can('manage_options')) to the spice_starter_sites_importer_creater function.

Recommended fix Moderate confidence

Plugin version higher than 1.2.5 (check WordPress plugin repository for latest release)

  1. Check the current version of the Spice Starter Sites plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate 'Spice Starter Sites' and verify the current version number
  4. If the installed version is 1.2.5 or lower, navigate to Plugins > Add New > Upload Plugin or go to the WordPress plugin repository to download the latest version
  5. Upload and install the updated plugin, or click 'Update Now' if an update is available
  6. After updating, verify the new version number confirms the update was successful
  7. Test that the demo import functionality still works correctly for authorized users

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8430 — 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-8430 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