dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-7410

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 My Custom CSS PHP & ADS plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.3. This is due the plugin not preventing direct access to the /my-custom-css/vendor/mobiledetect/mobiledetectlib/export/exportToJSON.php file and and the file displaying/generating the full path. 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 My Custom CSS PHP & ADS WordPress plugin fails to prevent direct access to an included third-party library file at /my-custom-css/vendor/mobiledetect/mobiledetectlib/export/exportToJSON.php, which when requested directly outputs the full server filesystem path. This is a classic Full Path Disclosure vulnerability allowing unauthenticated remote attackers to discover internal path information.

MitigationBlock direct access to the vulnerable exportToJSON.php file (e.g., via .htaccess deny rules or adding a direct-access check at the file's top), or update to a patched version once available from the vendor. If using a WAF, ensure path disclosure rules are enabled.

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 the plugin is installed
    Check for the presence of the /my-custom-css directory in your WordPress wp-content/plugins folder. You can use FTP, SSH, or a file manager to list the plugins directory contents.
    Affected if The /my-custom-css directory exists in wp-content/plugins
  2. Check the plugin version
    Open /wp-content/plugins/my-custom-css/readme.txt and look for the version number in the header section, or check the plugin's main PHP file for the Version header comment.
    Affected if You cannot determine the version or the version is unknown/older than any patched release
  3. Confirm the vulnerable file exists
    Check if the file /my-custom-css/vendor/mobiledect/mobiledetectlib/export/exportToJSON.php exists on the server. Use a file listing command or file manager to verify its presence.
    Affected if The exportToJSON.php file exists in the vendor directory
  4. Test for full path disclosure
    Make an HTTP GET request to /wp-content/plugins/my-custom-css/vendor/mobiledetect/mobiledetectlib/export/exportToJSON.php using curl, browser, or any HTTP client. Inspect the response body for server filesystem paths.
    Affected if The response contains absolute server paths such as /var/www/ or C:\inetpub\ or similar directory structures
  5. Verify direct access is not blocked
    Check the plugin directory for .htaccess rules or any PHP files containing 'defined(ABSPATH)' exit checks at the top that should block direct access. Review .htaccess in the plugin root and vendor directories.
    Affected if No access controls exist and the vulnerable file is directly accessible via HTTP

If the plugin is installed, the vulnerable exportToJSON.php file exists, and requesting it directly returns server filesystem paths in the response, then your environment is affected by this Full Path Disclosure vulnerability.

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 exportToJSON.php file (e.g., via .htaccess deny rules or adding a direct-access check at the file's top), or update to a patched version once available from the vendor. If using a WAF, ensure path disclosure rules are enabled.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.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-7410 — 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-7410 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