dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-6560

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-20
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 Addonify – Quick View For WooCommerce plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.2.16. 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 Addonify – Quick View For WooCommerce plugin for WordPress is vulnerable to Full Path Disclosure (FPD) in all versions up to 1.2.16. The vulnerability exists because the plugin includes the mobiledetect library without restricting direct access to its files. Unauthenticated attackers can directly request these files to reveal the server's absolute filesystem path.

MitigationUpdate the plugin to version 1.2.17 or later, which should include the fix. Alternatively, manually protect the mobiledetect files by adding direct-access restrictions in .htaccess or moving the library outside the web root.

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. Confirm plugin installation and version
    Check the WordPress admin under Plugins > Installed Plugins, or inspect the plugin's main PHP file header for the 'Version' field. Common path: /wp-content/plugins/addonify-quick-view/
    Affected if The installed version is 1.2.16 or lower (all versions up to 1.2.16 are affected)
  2. Locate the mobiledetect library files
    Search the plugin directory for files named 'mobiledetect' or within a 'mobiledetect' folder. Common pattern: /wp-content/plugins/addonify-quick-view/includes/vendor/mobiledetect/
    Affected if The mobiledetect library files exist within the plugin directory and are accessible via web requests
  3. Verify direct access is not blocked
    Attempt to directly access a mobiledetect file (e.g., request the PHP file directly via browser or curl). Also check if .htaccess restrictions exist in the mobiledetect directory to prevent direct access.
    Affected if The mobiledetect PHP files can be requested directly without redirect or 403 error, exposing the server's absolute filesystem path in any error output

A user is affected if the plugin version is 1.2.16 or lower AND the mobiledetect library files are directly accessible via web requests, allowing unauthenticated attackers to obtain the server's absolute 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.2.17 or later, which should include the fix. Alternatively, manually protect the mobiledetect files by adding direct-access restrictions in .htaccess or moving the library outside the web root.

Recommended fix Moderate confidence

Addonify – Quick View For WooCommerce version 1.2.17 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Addonify – Quick View For WooCommerce' in the plugin list
  4. Check the current version number to confirm it is 1.2.16 or below
  5. If an update is available, click 'Update Now' to install the latest version
  6. Alternatively, download the updated plugin from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  7. After updating, verify the new version number reflects the update

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

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