CVE-2024-43345
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 PluginOps Landing Page Builder allows PHP Local File Inclusion.This issue affects Landing Page Builder: from n/a through 1.5.2.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 confidencePath traversal vulnerability in PluginOps Landing Page Builder WordPress plugin (versions through 1.5.2.0) allows attackers to read arbitrary files on the server via PHP Local File Inclusion by manipulating path references in vulnerable parameters.
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 PluginOps Landing Page Builder is installedAccess WordPress admin dashboard under Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for the 'olw-page-builder' or 'pluginops-landing-page-builder' folderAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionCheck the plugin's main PHP file header (usually in the plugin root folder) for the 'Version' comment, or view the version in the WordPress plugin repository entryAffected if The version is 1.5.2.0 or any earlier version
-
Identify accessible file inclusion endpointsReview plugin PHP files for include(), require(), or similar functions that accept user-supplied path parameters; common patterns include parameters like 'page', 'file', 'path', 'template', or 'slug' in GET/POST requestsAffected if The plugin contains dynamic file inclusion calls using unsanitized input from request parameters
-
Confirm the vulnerability is exploitableTest the identified parameters with traversal sequences (e.g., ../../../../etc/passwd) while monitoring server response; verify the application returns file contents or error messages revealing file accessAffected if The application returns content from files outside the intended directory or displays path-related errors
-
Check server configuration for LFI mitigationInspect PHP configuration (php.ini) for open_basedir restrictions and verify web server access controls; review if the plugin's includes are protected by authentication checksAffected if No authentication is required to access the vulnerable endpoint AND open_basedir is not configured to restrict file access
A user is affected if PluginOps Landing Page Builder version 1.5.2.0 or earlier is installed AND the plugin exposes file inclusion parameters that allow path traversal without authentication.
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 to a patched version of the plugin once released; alternatively, implement strict input validation with realpath() checks and block traversal sequences (.., /) in user-supplied path parameters.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.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-43345 — 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-43345 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