dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-11952

HIGH · 7.5 CVSS v3.1 Published 2024-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/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
The Classic Addons – WPBakery Page Builder plugin for WordPress is vulnerable to Limited Local PHP File Inclusion in all versions up to, and including, 3.0 via the 'style' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, and permissions granted by an Administrator, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. The vulnerability is limited to PHP files in a Windows environment.

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 Classic Addons plugin for WPBakery Page Builder contains a Local File Inclusion vulnerability via the 'style' parameter. Authenticated users with Contributor-level access can include arbitrary PHP files on Windows servers, leading to remote code execution.

MitigationUpdate the Classic Addons plugin to version 3.1 or later. Review and restrict user role permissions, especially for Contributor-level accounts, until the patch is applied.

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

CVSS:3.1/AV:N/AC:H/PR:L/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. Confirm Classic Addons plugin is installed
    Navigate to WordPress admin dashboard > Plugins and locate 'Classic Addons for WPBakery' in the installed plugins list. Alternatively, check the plugin directory at /wp-content/plugins/ for a folder named 'classic-addons' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In the WordPress Plugins page, click on the plugin to view details and read the version number. Alternatively, inspect the plugin's main PHP file or readme.txt in the plugin directory and look for a 'Version:' comment or tag.
    Affected if The version is below 3.1 (the patched version) or cannot be determined
  3. Verify Contributor-level user accounts exist
    In WordPress admin, go to Users > All Users and check for any accounts with the 'Contributor' role. Alternatively, query the wp_usermeta table filtering for wp_capabilities containing 'contributor'.
    Affected if At least one user account with Contributor role exists in the system
  4. Confirm the server operating system is Windows
    Check the server environment documentation, hosting control panel, or run a command such as 'php_uname' or check system environment variables. In WordPress, you can use a plugin or add phpinfo() to confirm the OS.
    Affected if The web server is running Windows (Windows Server or Windows-based hosting)
  5. Test access to the vulnerable 'style' parameter
    If authenticated as a Contributor, attempt a request to a page using WPBakery with the Classic Addons style parameter, such as: POST to an endpoint with 'style' parameter set to a path like '../../../../../windows/system32/drivers/etc/hosts'. Monitor for inclusion of arbitrary file contents.
    Affected if The server returns file contents from arbitrary paths, indicating LFI is exploitable

A user is affected if the Classic Addons plugin is installed with a version below 3.1, Contributor-level accounts exist, the server runs Windows, and the style parameter permits arbitrary file inclusion.

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 the Classic Addons plugin to version 3.1 or later. Review and restrict user role permissions, especially for Contributor-level accounts, until the patch is applied.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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