dbcve.org
Path TraversalWeakness · CWE-22

CVE-2023-24379

MEDIUM · 6.8 CVSS v3.1 Published 2024-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Web-Settler Landing Page Builder – Free Landing Page Templates allows Path Traversal.This issue affects Landing Page Builder – Free Landing Page Templates: from n/a through 3.1.9.9.

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

Path traversal vulnerability in Web-Settler Landing Page Builder WordPress plugin allows attackers to access files outside restricted directories by manipulating file path inputs. The vulnerability exists in versions up to 3.1.9.9, potentially enabling unauthorized file system access.

MitigationUpdate to the latest version of the plugin to obtain the security patch. Until then, restrict web server file permissions and monitor for suspicious path-based requests.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

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. Locate the plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Web-Settler Landing Page Builder' - the version is displayed below the plugin name. Alternatively, check the main plugin PHP file (often named landing-page-builder.php or similar in wp-content/plugins/) for a 'Version:' comment in the file header.
    Affected if The displayed version is 3.1.9.9 or any earlier version (e.g., 3.1.9, 3.1.8, etc.)
  2. Compare version to affected range
    Review the version number found in the previous step. The vulnerability affects versions up to and including 3.1.9.9. Any version number at or below 3.1.9.9 is within the affected range.
    Affected if The installed version is 3.1.9.9 or lower, or if the plugin does not show a version (older unmaintained installation)
  3. Confirm plugin is active
    In WordPress admin Plugins page, verify that the Web-Settler Landing Page Builder plugin shows as 'Active'. Path traversal can only be exploited when the vulnerable code is running.
    Affected if The plugin is currently active on the WordPress site
  4. Review web server access logs
    Examine Apache/nginx access logs (often in /var/log/apache2/, /var/log/nginx/, or your hosting control panel) for unusual requests containing '../' sequences or direct file path references targeting system files like /etc/passwd, wp-config.php, or other sensitive files.
    Affected if Log entries show path traversal attempts (sequences like '..%2F', '../', or absolute paths like '/etc/') targeting the landing-page-builder functionality

A WordPress site is affected if the Web-Settler Landing Page Builder plugin is installed with version 3.1.9.9 or lower and the plugin is active, allowing potential path traversal attacks.

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

Update to the latest version of the plugin to obtain the security patch. Until then, restrict web server file permissions and monitor for suspicious path-based requests.

Recommended fix Moderate confidence

3.1.10 or latest available version (after 3.1.9.9)

  1. 1. Backup the WordPress site and database before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Find 'Landing Page Builder – Free Landing Page Templates' (by Web-Settler)
  4. 4. If update is available, click 'Update Now' to install the latest version
  5. 5. If no update is shown, manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the updated version number is 3.1.10 or higher after update
  7. 7. Test the plugin functionality to ensure the path traversal vulnerability is resolved

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.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-2023-24379 — 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-2023-24379 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