dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-7416

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 Reveal Template plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.7. This is due to the plugin allowing direct access to the bootstrap.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 · high confidence

The Reveal Template WordPress plugin (versions up to 3.7) has a Full Path Disclosure vulnerability. The plugin's bootstrap.php file can be accessed directly and has PHP's display_errors enabled, causing the full server path to be exposed when errors occur. While this disclosure alone has limited impact, it aids attackers in reconnaissance for chained exploits.

MitigationUpdate the Reveal Template plugin to version 3.8 or later, or disable PHP display_errors in php.ini/server configuration to prevent path disclosure.

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. Check if Reveal Template plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'reveal-template' or similar.
    Affected if The Reveal Template plugin is found in the WordPress installation
  2. Verify the installed plugin version
    In WordPress admin, go to Plugins > Reveal Template and view the version number. Alternatively, check the plugin's main PHP file or readme.txt for the Version header.
    Affected if The version is 3.7 or lower (the vulnerability affects versions up to 3.7)
  3. Locate the bootstrap.php file
    Check for the presence of bootstrap.php in the plugin directory, typically at /wp-content/plugins/reveal-template/bootstrap.php or similar path within the plugin folder.
    Affected if The bootstrap.php file exists in the plugin directory
  4. Test if bootstrap.php is directly accessible
    Attempt to access the bootstrap.php file directly via browser (e.g., https://yourdomain.com/wp-content/plugins/reveal-template/bootstrap.php). Check if the file can be loaded without WordPress initialization.
    Affected if The file is accessible and loads without requiring WordPress core to initialize
  5. Check PHP display_errors setting
    Create a PHP test file with '<?php phpinfo(); ?>' or check php.ini / .htaccess / site configuration for the display_errors setting. On Linux servers, run: grep -r 'display_errors' /etc/php/
    Affected if PHP display_errors is set to On (this enables the path disclosure when errors occur)

A user is affected if the Reveal Template plugin version is 3.7 or lower AND the bootstrap.php file is directly accessible AND PHP display_errors is enabled, as these conditions together allow full server 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

Update the Reveal Template plugin to version 3.8 or later, or disable PHP display_errors in php.ini/server configuration to prevent path disclosure.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (verify current version at plugins.trac.wordpress.org)

  1. Check the WordPress plugin repository at plugins.trac.wordpress.org or wordpress.org for the latest version of the Reveal Template plugin
  2. Compare the current installed version with the latest available version
  3. If the current version is 3.7 or below, update to the latest version available in the repository
  4. After updating, verify the bootstrap.php file is no longer directly accessible
  5. Confirm display_errors is disabled in php.ini or through web server configuration to prevent information disclosure

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing0.5 h
  • Review / QA0.5 h
3.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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