dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-6556

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-10
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 SmartCrawl WordPress SEO checker, SEO analyzer, SEO optimizer plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.10.8. This is due the plugin utilizing mobiledetect without preventing direct access to the files. 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 SmartCrawl WordPress SEO plugin includes the mobiledetect library without proper access controls, allowing unauthenticated attackers to directly request these library files via the web browser. This reveals the full server filesystem path of the WordPress installation, which can be used as reconnaissance to aid in targeting other vulnerabilities.

MitigationUpdate SmartCrawl plugin to version 3.10.9 or later, which contains the proper fix. Alternatively, configure web server rules (e.g., .htaccess) to deny direct access to all mobiledetect files within the plugin directory.

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 if SmartCrawl plugin is installed
    Check the WordPress plugins directory or use wp-cli: wp plugin list --name=smartcrawl
    Affected if SmartCrawl plugin is present in the WordPress installation
  2. Determine installed SmartCrawl version
    Check wp-content/plugins/smartcrawl/seo-plugin-wp.php header or use: wp plugin get smartcrawl --field=version
    Affected if Version is lower than 3.10.9 (vulnerable)
  3. Locate mobiledetect library files
    Search for mobiledetect files in the plugin directory: find /path/to/wp-content/plugins/smartcrawl -name '*mobiledetect*' -o -name 'Mobile_Detect.php'
    Affected if mobiledetect library files exist within the SmartCrawl plugin directory
  4. Test for direct access vulnerability
    Using a web browser or curl, attempt to access: https://yourdomain.com/wp-content/plugins/smartcrawl/includes/core/class-mobile-detect.php (or similar mobiledetect path)
    Affected if The file is accessible and returns the full server filesystem path in error messages or source
  5. Verify path disclosure occurs
    Trigger a PHP error in the accessed file by requesting it directly; examine the response for absolute server paths
    Affected if Full server filesystem paths (e.g., /var/www/html/wp-content/...) are exposed in the response

If SmartCrawl plugin version is below 3.10.9 AND mobiledetect library files are directly accessible via web browser exposing server paths, the environment is affected by CVE-2024-6556.

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 SmartCrawl plugin to version 3.10.9 or later, which contains the proper fix. Alternatively, configure web server rules (e.g., .htaccess) to deny direct access to all mobiledetect files within the plugin directory.

Recommended fix High confidence

SmartCrawl 3.10.9 or later

  1. Update the SmartCrawl WordPress plugin to version 3.10.9 or later through the WordPress admin dashboard under Plugins > Installed Plugins
  2. Alternatively, update via FTP or your hosting control panel file manager by replacing the /wp-content/plugins/smartcrawl-seo/ directory with the updated version
  3. After updating, verify the fix by attempting to access the mobiledetect library files directly (e.g., /wp-content/plugins/smartcrawl-seo/includes/lib/mobiledetect/mobile-detect.php) - they should no longer be accessible or return a 403/404 error
  4. Confirm the plugin is functioning normally after the update by running a crawl or SEO check

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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