CVE-2024-7382
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 · uneditedThe Linkify Text plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.9.1. This is due to the plugin utilizing bootstrap and leaving test files with 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 confidenceThe Linkify Text WordPress plugin (versions up to 1.9.1) contains a Full Path Disclosure vulnerability. The plugin utilizes Bootstrap and leaves test files accessible with PHP display_errors enabled, causing the server to output the full filesystem path when those test files are accessed. Unauthenticated attackers can trigger this by requesting the exposed test files.
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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed version of the Linkify Text pluginIn WordPress admin, go to Plugins > Installed Plugins and look for Linkify Text to see the version number, or inspect the plugin header in wp-content/plugins/linkify-text/readme.txt or the main plugin PHP fileAffected if The version is 1.9.1 or lower
-
Identify test files in the plugin directoryBrowse the plugin directory at wp-content/plugins/linkify-text/ and look for any test, debug, sample, or example files with .php extensions, especially those related to Bootstrap or debugging utilitiesAffected if Any PHP test or debug files are present in the plugin directory
-
Verify PHP display_errors settingCheck your php.ini file for display_errors = On, or create a PHP info page or check via command line: php -i | grep display_errors, or look for this setting in your hosting control panelAffected if PHP display_errors is enabled (set to On or 1)
-
Test for full path disclosureIf test files exist and display_errors is on, attempt to access potential test files via HTTP request (for example: wp-content/plugins/linkify-text/test/*.php or similar debug files) and observe if the server response includes a full filesystem pathAffected if Accessing test files reveals the full server path in error messages
You are affected if the Linkify Text plugin version is 1.9.1 or below, PHP display_errors is enabled, and the plugin directory contains accessible test files that can be triggered by unauthenticated requests to disclose the full path.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the plugin to a version beyond 1.9.1 when available, or manually remove the test files from the plugin directory and ensure PHP display_errors is disabled in the production php.ini configuration.
- Consultation1.0 h
- Implementation1.0 h
- Testing0.5 h
- Review / QA0.5 h
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 locallyCheck whether your project pulls in CVE-2024-7382 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-7382 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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