dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-47645

HIGH · 7.5 CVSS v3.1 Published 2024-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 Danish Ali Malik Top Bar – PopUps – by WPOptin wpoptin allows PHP Local File Inclusion.This issue affects Top Bar – PopUps – by WPOptin: from n/a through <= 2.0.1.

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

A Path Traversal vulnerability in the Top Bar – PopUps – by WPOptin WordPress plugin (versions <= 2.0.1) allows unauthenticated attackers to perform Local File Inclusion (LFI) by manipulating file path parameters with directory traversal sequences (e.g., ../../../). This can enable reading sensitive files on the server such as wp-config.php, exposing database credentials and other configuration data.

MitigationUpdate the plugin to the latest version which should include proper path validation using basename(), realpath(), or whitelist-based file access controls to prevent directory traversal. Until patched, consider disabling the plugin or restricting access via web server rules.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Locate the WPOptin plugin installation
    Check your WordPress plugins directory (wp-content/plugins/) for a folder containing 'wpoptin', 'top-bar', or 'popups' in the name. Common folder names may include 'wpoptin' or 'optin-wp'. List all plugin directories to identify if this plugin is present.
    Affected if The plugin folder exists in wp-content/plugins/ and contains files from the Top Bar PopUps plugin.
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually the primary PHP file in the plugin folder) and look for the plugin header comment containing 'Version:' followed by a version number. Alternatively, check the readme.txt file for the 'Stable tag:' or 'Version:' entry.
    Affected if The version number displayed is 2.0.1 or lower (e.g., 2.0.1, 2.0.0, 1.x.x).
  3. Confirm the plugin is active
    Log into the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and check if the Top Bar - PopUps - by WPOptin plugin is listed with an 'Active' status.
    Affected if The plugin shows as Active on the WordPress plugins page.
  4. Identify the vulnerable file inclusion endpoint
    Review the plugin PHP files for functions that accept file path parameters (look for include, require, file_get_contents, readfile, or similar file operations). Search for parameters that accept user input and are used in file operations without proper sanitization.
    Affected if The plugin contains PHP code that processes a file path parameter and includes/reads files based on that parameter without proper path validation.

Your environment is affected if the Top Bar - PopUps - by WPOptin plugin is installed, active, and running version 2.0.1 or lower, with a file inclusion feature that accepts path parameters without validation.

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 plugin to the latest version which should include proper path validation using basename(), realpath(), or whitelist-based file access controls to prevent directory traversal. Until patched, consider disabling the plugin or restricting access via web server rules.

Recommended fix Moderate confidence

Latest available version of Top Bar – PopUps – by WPOptin (version higher than 2.0.1)

  1. Check the current version of the Top Bar – PopUps – by WPOptin plugin installed on your WordPress site
  2. If the installed version is <= 2.0.1, log in to the WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Find Top Bar – PopUps – by WPOptin and check for available updates
  5. If an update is available, update the plugin to the latest version
  6. If no update is available through the WordPress admin, visit the WordPress plugin repository or contact the vendor directly for the patched version
  7. Verify the plugin has been updated to a version newer than 2.0.1

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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