dbcve.org
BetterdocsWordPress extension · Wpdeveloper

CVE-2024-43129

HIGH · 8.8 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 3.5.9 or later.
See remediation →
94/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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in WPDeveloper BetterDocs allows PHP Local File Inclusion.This issue affects BetterDocs: from n/a through 3.5.8.

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

Path traversal vulnerability in BetterDocs WordPress plugin allows attackers to manipulate file paths to include arbitrary PHP files from the server, potentially enabling code execution or sensitive data exposure. The vulnerability stems from insufficient validation of user-supplied path inputs in the plugin's functionality.

MitigationUpdate BetterDocs to the latest patched version if available. If no patch exists, disable the plugin or implement WAF rules to block directory traversal patterns in requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BetterdocsWordPress extension
Affected:< 3.5.9

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 BetterDocs plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the betterdocs folder
    Affected if BetterDocs plugin is present on the WordPress site
  2. Check installed BetterDocs version
    In WordPress admin, go to Plugins > Installed Plugins and find the BetterDocs entry to view the version number, or inspect the main plugin file (betterdocs.php) and look for the Version header comment
    Affected if Version is lower than 3.5.9 (e.g., 3.5.8, 3.5.0, etc.) or if the version cannot be determined
  3. Identify if path traversal features are accessible
    Review the plugin settings and publicly accessible endpoints that handle file paths or includes. Common paths to check: any AJAX actions or shortcodes that accept file path parameters, and any template/include functionality that loads files based on user input
    Affected if The plugin exposes any functionality that accepts file path parameters without proper sanitization (look for parameters like 'file', 'path', 'template', 'include', or similar in HTTP requests)
  4. Review access logs for suspicious path traversal patterns
    Examine web server access logs (Apache, Nginx) and WordPress debug logs for requests containing '../' sequences, absolute paths like '/wp-content/', or attempts to access PHP files outside intended directories in conjunction with BetterDocs-related URLs
    Affected if Logs show requests with directory traversal patterns (../) targeting PHP files on URLs associated with BetterDocs functionality

Your site is affected if BetterDocs version is below 3.5.9 and the plugin exposes any file path handling functionality that could be manipulated for directory traversal.

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
Upgrade available Upgrade to 3.5.9 or later
Fixed in 3.5.9
Interim mitigation

Update BetterDocs to the latest patched version if available. If no patch exists, disable the plugin or implement WAF rules to block directory traversal patterns in requests.

Recommended fix High confidence

BetterDocs version 3.5.9

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate BetterDocs in the plugin list
  4. Check if the current version is below 3.5.9
  5. If vulnerable, click 'Update Now' to upgrade to version 3.5.9 or later
  6. Alternatively, download BetterDocs 3.5.9 from the official WordPress repository and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the new version is showing as 3.5.9 or higher
  8. Review the plugin changelog for any potential compatibility issues with other installed plugins or themes
Caveat Review plugin changelog for any breaking changes or deprecations before updating in production environments

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

Fix this in Betterdocs 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 the upgrade done

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-43129 — 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-43129 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