dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-27972

CRITICAL · 9.9 CVSS v3.1 Published 2024-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Control of Generation of Code ('Code Injection') vulnerability in Jack Arturo WP Fusion Lite wp-fusion-lite.This issue affects WP Fusion Lite: from n/a through <= 3.41.24.

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

This is a code injection vulnerability in the WP Fusion Lite WordPress plugin that allows attackers to inject and execute malicious server-side code due to improper control of code generation. The vulnerability affects all versions up to and including 3.41.24, potentially allowing full site compromise.

MitigationUpdate WP Fusion Lite to the latest version immediately. If patching is not possible, disable the plugin and review the WordPress installation for signs of compromise.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Confirm WP Fusion Lite is installed
    Log in to WordPress admin and go to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'wp-fusion-lite'
    Affected if The plugin folder exists in the WordPress installation
  2. Identify the installed version number
    In WordPress admin, find WP Fusion Lite in the plugins list and read the version number displayed below the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/wp-fusion-lite/includes/class-main.php for the 'Version' comment
    Affected if The version number is at or below 3.41.24
  3. Verify the plugin is active
    In WordPress admin > Plugins, check if WP Fusion Lite shows as 'Active' under the plugin status column
    Affected if The plugin is currently active and running (inactive plugins would not be exploitable)
  4. Check for unauthorized code additions
    Review the /wp-content/plugins/wp-fusion-lite/ directory for any recently modified PHP files or unfamiliar files, particularly in the includes/ subfolder where the vulnerable code resides
    Affected if Unexpected PHP files exist or known files have been modified outside of normal updates

A WordPress site is affected if WP Fusion Lite version 3.41.24 or lower is installed and active, exposing the site to potential code injection and full compromise.

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

Update WP Fusion Lite to the latest version immediately. If patching is not possible, disable the plugin and review the WordPress installation for signs of compromise.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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