dbcve.org
Olive One Click Demo ImportWordPress extension · Olivethemes

CVE-2024-38749

HIGH · 7.5 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to after 1.1.2 or later.
See remediation →
84/100
Remediation priority · High
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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Olive Themes Olive One Click Demo Import allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Olive One Click Demo Import: from n/a through 1.1.2.

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 · moderate confidence

The Olive One Click Demo Import plugin for WordPress (versions through 1.1.2) contains a vulnerability allowing unauthorized access to sensitive information and functionality. The plugin fails to properly constrain access control lists (ACLs), enabling unauthenticated actors to access the demo import functionality and potentially retrieve sensitive configuration data, credentials, or content that should be restricted to administrators.

MitigationUpdate to the latest version of Olive One Click Demo Import if available, or restrict access to the demo import functionality by implementing proper authentication and authorization checks, limiting access to authenticated administrators 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
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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 plugin installation
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins and look for 'Olive One Click Demo Import' or 'Olivethemes Olive One Click Demo Import', or inspect the wp-content/plugins directory for a folder containing 'olive' and 'demo-import' in the name
    Affected if The plugin is installed and active in the WordPress environment
  2. Check installed version
    Open the main plugin PHP file in wp-content/plugins/[olive-demo-import-folder]/ and locate the 'Version:' field in the plugin header comment block at the top of the file
    Affected if The version number found is 1.1.2 or lower (any version through 1.1.2)
  3. Inspect demo import endpoint accessibility
    Check the plugin's PHP files (commonly import.php, demo-import.php, or similar files handling the import functionality) for how access control is implemented. Look for capability checks like 'current_user_can' or 'is_user_logged_in' before executing import logic
    Affected if No capability checks exist before the demo import functionality executes, or the code only checks for a simple boolean without verifying user roles
  4. Verify AJAX/action handlers
    If the plugin uses AJAX endpoints (wp-admin/admin-ajax.php or wp-json/ routes), examine the callback functions registered for demo import actions. Check if they verify authentication and authorization before returning sensitive data
    Affected if AJAX or REST API handlers for demo import do not require authentication or perform insufficient capability checks

You are affected if the Olive One Click Demo Import plugin is installed with version 1.1.2 or lower and the demo import functionality lacks proper authentication and capability verification before exposing sensitive data or administrative 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.

From vendor data
Upgrade available Upgrade to a release after 1.1.2
Interim mitigation

Update to the latest version of Olive One Click Demo Import if available, or restrict access to the demo import functionality by implementing proper authentication and authorization checks, limiting access to authenticated administrators only.

Fix this in Olive One Click Demo Import Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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