dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-7414

MEDIUM · 5.3 CVSS v3.1 Published 2024-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 PDF Builder for WPForms plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.2.116. This is due to the plugin allowing direct access to the composer-setup.php file which has display_errors on. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

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

The PDF Builder for WPForms WordPress plugin is vulnerable to Full Path Disclosure due to direct access to composer-setup.php with display_errors enabled. Unauthenticated attackers can retrieve the full server path, which aids in reconnaissance but requires another vulnerability for actual damage.

MitigationDisable PHP display_errors in php.ini or web server configuration, and/or restrict direct access to composer-setup.php. If a patched version is available, update the plugin.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Verify PDF Builder for WPForms plugin is installed
    Check the WordPress plugins directory for the 'wpforms-pdf-builder' or 'pdf-builder-for-wpforms' folder, or list installed plugins via wp-cli: wp plugin list --name='*pdf*'
    Affected if The plugin folder exists in wp-content/plugins/
  2. Locate composer-setup.php in the plugin
    Check the plugin directory for composer-setup.php file: ls wp-content/plugins/*pdf*/composer-setup.php or find wp-content/plugins/ -name 'composer-setup.php'
    Affected if The file composer-setup.php exists within the plugin directory
  3. Confirm PHP display_errors is enabled
    Check php.ini or run: php -i | grep display_errors, or create a PHP info page to check the display_errors setting
    Affected if display_errors is set to On in PHP configuration
  4. Test for path disclosure via direct access
    Make an HTTP request to the composer-setup.php file directly: curl -I https://yourdomain.com/wp-content/plugins/*/composer-setup.php and examine if full server path appears in error output
    Affected if Requesting composer-setup.php directly reveals the full server path in an error message

You are affected if the PDF Builder for WPForms plugin is installed, composer-setup.php is directly accessible, and PHP display_errors is enabled, allowing unauthenticated path disclosure.

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

Disable PHP display_errors in php.ini or web server configuration, and/or restrict direct access to composer-setup.php. If a patched version is available, update the plugin.

Recommended fix Moderate confidence

Version 1.2.117 or later of PDF Builder for WPForms

  1. 1. Check the current version of the PDF Builder for WPForms plugin installed on your WordPress site.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Locate PDF Builder for WPForms and note the current version.
  4. 4. Visit the WordPress plugin repository or contact the plugin developer to obtain version 1.2.117 or later which should contain the fix for this Full Path Disclosure vulnerability.
  5. 5. Update the plugin to the latest available version that addresses CVE-2024-7414.
  6. 6. Verify that the composer-setup.php file is no longer directly accessible or that display_errors is disabled.
  7. 7. Test the plugin functionality to ensure the update did not break existing features.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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