CVE-2024-56286
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in webcodingplace Classic Addons – WPBakery Page Builder classic-addons-wpbakery-page-builder-addons allows PHP Local File Inclusion.This issue affects Classic Addons – WPBakery Page Builder: from n/a through <= 3.0.
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 confidenceA path traversal vulnerability in the Classic Addons – WPBakery Page Builder plugin allows remote attackers to perform Local File Inclusion (LFI) attacks. The plugin fails to properly validate file path inputs, enabling attackers to use directory traversal sequences (e.g., ../../) to include and potentially execute arbitrary PHP files from the server's filesystem.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Classic Addons - WPBakery Page Builder plugin is installedLog into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Classic Addons - WPBakery Page Builder' in the list of active plugins.Affected if The plugin appears in the installed plugins list, regardless of activation status, the environment could be vulnerable.
-
Identify installed plugin versionIn the WordPress admin, go to Plugins > Installed Plugins. Click on the plugin name or view the plugin details to find the version number displayed.Affected if The installed version falls within any affected version range for this CVE.
-
Check if file inclusion or template features are accessibleExamine the plugin settings and shortcodes available. Look for any features that accept file paths or template parameters, particularly in frontend-facing components.Affected if The plugin exposes any functionality that accepts file path parameters without sanitization, the path traversal vulnerability is exploitable.
-
Inspect plugin file structure for vulnerable inclusion functionsAccess the site via FTP or file manager. Navigate to wp-content/plugins/classic-addons-for-wpbakery/. Search PHP files for functions like include, require, include_once, or require_once that use user-supplied input without sanitization.Affected if Any PHP file within the plugin uses dynamic file inclusion with unsanitized variables derived from request parameters.
If the Classic Addons - WPBakery Page Builder plugin is installed and the installed version is within the affected range, or if the plugin exposes file inclusion functionality using unsanitized path parameters, the environment is vulnerable to CVE-2024-56286.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the Classic Addons – WPBakery Page Builder plugin to the latest version, or implement proper input validation and path sanitization on all file inclusion functions to restrict access to allowed directories only.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-56286 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-56286 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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