Spam Free WordPress <= 1.9.3 - Full Path Disclosure
Strategic Overview
- Status
- Patched in 2.0
- Affected Plugin
- Spam Free WordPress
- Affected Version
<= 1.9.3- CVSS
- 7.5High
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE pending
At a glance
This record tracks a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Spam Free WordPress WordPress plugin, affecting versions <= 1.9.3. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 2.0; sites on affected versions should update now. Disclosed January 2013, reported by Akastep.
Vulnerability Overview
The Spam Free WordPress plugin for WordPress is vulnerable to full path disclosure in versions up to, and including, 1.9.3 via various files. This makes it possible for unauthenticated attackers to extract sensitive data which consists of full application path details that can be used to exploit additional vulnerabilities that may require that information.
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. A successful exploit has high impact on confidentiality.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Spam Free WordPress <= 1.9.3 takes a caller who can reach the endpoint. 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 Spam Free WordPress the fix is 2.0: builds <= 1.9.3 are affected, anything from 2.0 onward is not.
Remediation
Update to version 2.0, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Spam Free WordPress 2.0 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in Spam Free WordPress
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C