dbcve.org
Wp Import Export LiteWordPress extension · Vjinfotech

CVE-2024-31308

HIGH · 7.2 CVSS v3.1 Published 2024-04-07
Fix available
A fix is available. Upgrade to 3.9.27 or later.
See remediation →
78/100
Remediation priority · High
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
Deserialization of Untrusted Data vulnerability in VJInfotech WP Import Export Lite.This issue affects WP Import Export Lite: from n/a through 3.9.26.

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

A deserialization of untrusted data vulnerability exists in the WP Import Export Lite WordPress plugin. The plugin appears to use PHP's unserialize() function on data from an untrusted source (likely an imported file or request parameter), which can be exploited to inject PHP objects and potentially achieve remote code execution.

MitigationUpdate WP Import Export Lite to the latest patched version. If no patched version is available, disable the plugin until a fix is released and verify no malicious payloads were already injected.

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
Wp Import Export LiteWordPress extension
Affected:< 3.9.27

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

CVSS:3.1/AV:N/AC:L/PR:H/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 WP Import Export Lite is installed
    Navigate to WordPress admin > Plugins and look for 'WP Import Export Lite' in the installed plugins list, or check the /wp-content/plugins/ directory for a folder named 'wp-import-export-lite' or similar
    Affected if The plugin is present on the WordPress installation
  2. Check the installed plugin version
    In WordPress admin > Plugins > WP Import Export Lite, click on the plugin name to view the version number. Alternatively, check the main plugin PHP file for a Version header comment
    Affected if The version number is less than 3.9.27 (e.g., 3.9.26, 3.9.25, etc.)
  3. Determine if the import functionality is accessible
    Check if the WordPress user has admin-level access to the plugin's import feature. Look for menu items labeled Import, Import Export, or similar under the WP Import Export Lite settings
    Affected if Authenticated administrators can access the plugin's import interface and supply data to it
  4. Inspect for unauthorized files or modifications
    Review the /wp-content/uploads/ directory and the /wp-content/plugins/ directory for unexpected PHP files, especially those with obfuscated code or suspicious names (e.g., shell.php, wp-cache.php, cached files). Check file modification timestamps around the time the import feature may have been used
    Affected if Unfamiliar PHP files exist in upload directories or plugin directories, or files were modified unexpectedly

You are affected if WP Import Export Lite version less than 3.9.27 is installed and the plugin's import functionality is accessible to your users.

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 3.9.27 or later
Fixed in 3.9.27
Interim mitigation

Update WP Import Export Lite to the latest patched version. If no patched version is available, disable the plugin until a fix is released and verify no malicious payloads were already injected.

Recommended fix High confidence

WP Import Export Lite 3.9.27

  1. Update WP Import Export Lite plugin to version 3.9.27 or later through the WordPress admin dashboard under Plugins > Installed Plugins > WP Import Export Lite > Update Now
  2. Verify the update was successful by checking the plugin version number after updating
  3. If using automated WordPress management tools, push the update to production environments

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

Fix this in Wp Import Export Lite 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 the upgrade done

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-31308 — 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-31308 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