dbcve.org
Olive One Click Demo ImportWordPress extension · Olivethemes

CVE-2024-2702

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-20
Fix available
A fix is available. Upgrade to 1.1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in Olive Themes Olive One Click Demo Import allows importing settings and data, ultimately leading to XSS.This issue affects Olive One Click Demo Import: from n/a through 1.1.1.

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

Missing authorization check in the Olive One Click Demo Import plugin allows unauthenticated attackers to import arbitrary settings and data through the demo import functionality. Since the imported data is stored and rendered on the WordPress site, this enables stored XSS attacks with critical severity.

MitigationUpdate to the patched version of Olive One Click Demo Import. If no patch is available, disable the plugin until a fix is released. The fix requires adding proper capability checks and nonce verification to the import endpoints.

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
Olive One Click Demo ImportWordPress extension
Affected:< 1.1.2

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
High
Integrity
High
Availability
High

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

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 Olive One Click Demo Import plugin is installed
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Olivethemes Olive One Click Demo Import' in the list of active or inactive plugins.
    Affected if The plugin appears in the installed plugins list.
  2. Check installed plugin version
    On the Plugins page, click 'View Details' next to Olive One Click Demo Import, or access the main plugin file (usually in wp-content/plugins/olive-one-click-demo-import/olive-one-click-demo-import.php) and look for the 'Version' header in the plugin comments.
    Affected if The version number displayed is lower than 1.1.2 (for example, 1.0.0, 1.1.0, 1.1.1).
  3. Inspect demo import endpoint accessibility
    Examine the plugin directory for PHP files handling import functionality (typically files named import.php, demo-import.php, or similar). Look for AJAX handlers or direct action endpoints that process import requests.
    Affected if The import handler files exist and there is no visible capability check (like current_user_can) or nonce verification at the entry points.
  4. Test unauthorized import capability
    Using a tool like curl, send a POST request to the plugin's import AJAX endpoint (commonly at /wp-admin/admin-ajax.php with action 'olive_demo_import' or similar) without authentication credentials.
    Affected if The server accepts the request and returns a successful response without requiring authentication or returning a 401/403 error.

The environment is affected if the Olive One Click Demo Import plugin is installed with a version lower than 1.1.2 and the demo import endpoint accepts unauthenticated requests.

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.1.2 or later
Fixed in 1.1.2
Interim mitigation

Update to the patched version of Olive One Click Demo Import. If no patch is available, disable the plugin until a fix is released. The fix requires adding proper capability checks and nonce verification to the import endpoints.

Recommended fix High confidence

1.1.2 or later

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find 'Olive One Click Demo Import' in the plugin list.
  5. 5. Check if the current version is below 1.1.2.
  6. 6. If update available, click 'Update Now' to upgrade to version 1.1.2 or later.
  7. 7. Alternatively, download the latest version from the WordPress Plugin Repository or Olive Themes.
  8. 8. Verify the update was successful by checking the plugin version.

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

Fix this in Olive One Click Demo Import Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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