dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-7411

MEDIUM · 5.3 CVSS v3.1 Published 2024-08-15
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 Newsletters plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 4.9.9. This is due the plugin not preventing direct access to the /vendor/mobiledetect/mobiledetectlib/export/exportToJSON.php. 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 Newsletters WordPress plugin fails to prevent direct access to an included vendor file at /vendor/mobiledetect/mobiledetectlib/export/exportToJSON.php. When accessed directly, this file exposes the server's full filesystem path, which can help attackers enumerate the application's directory structure for use in targeted attacks.

MitigationBlock direct access to the vulnerable PHP file via .htaccess/rules or remove the unused export file from the vendor directory; update the plugin to version 4.9.10 or later when available.

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. Identify the Newsletters plugin installation
    Navigate to WordPress admin > Plugins and locate the 'Newsletters' plugin, or inspect the /wp-content/plugins/ directory for a 'newsletters' folder. Check the plugin header or version file for the installed version number.
    Affected if The plugin is installed and the version is earlier than 4.9.10 (or the version cannot be determined but the vulnerable file exists)
  2. Locate the vulnerable vendor file
    Check if the file /vendor/mobiledetect/mobiledetectlib/export/exportToJSON.php exists within the Newsletters plugin directory (typically /wp-content/plugins/newsletters/vendor/mobiledetect/mobiledetectlib/export/exportToJSON.php).
    Affected if The file exists in the plugin directory, indicating the vulnerable component is present
  3. Test direct access to the export file
    Attempt to access the file directly via HTTP request to: https://yourdomain.com/wp-content/plugins/newsletters/vendor/mobiledetect/mobiledetectlib/export/exportToJSON.php. If the request succeeds and displays JSON output containing filesystem paths, the vulnerability is present.
    Affected if The file is accessible via direct HTTP request and exposes the server's full filesystem path in the response
  4. Verify access control via .htaccess
    Inspect the .htaccess file in the /vendor/ directory (if present) or the plugin root for rules blocking direct access to PHP files in the vendor directory. Check for directives like 'deny from all' or RewriteRule conditions protecting /vendor/ paths.
    Affected if No .htaccess protection exists for the vendor directory and the file is directly accessible

The environment is affected if the Newsletters plugin is installed with a version prior to 4.9.10 (or an unknown version) AND the vulnerable exportToJSON.php file exists and is directly accessible, exposing the filesystem path.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Block direct access to the vulnerable PHP file via .htaccess/rules or remove the unused export file from the vendor directory; update the plugin to version 4.9.10 or later when available.

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