Addonify – Quick View For WooCommerce <= 1.2.16 - Unauthenticated Full Path Dislcosure
Strategic Overview
- Status
- Patched in 1.2.17
- Affected Plugin
- Addonify – Quick View For WooCommerce
- Affected Version
<= 1.2.16- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2024-6560
At a glance
CVE-2024-6560 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Addonify WordPress plugin, affecting versions <= 1.2.16. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.17; sites on affected versions should update now. Disclosed July 2024, reported by stealthcopter.
Vulnerability Overview
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 Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Addonify <= 1.2.16 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Addonify the fix is 1.2.17: builds <= 1.2.16 are affected, anything from 1.2.17 onward is not.
Remediation
Update to version 1.2.17, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Addonify 1.2.17 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Addonify – Quick View For WooCommerce
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C