BulletProof Security <= 5.1 - Sensitive Information Disclosure
Strategic Overview
- Status
- Patched in 5.2
- Affected Plugin
- BulletProof Security
- Affected Version
<= 5.1- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2021-39327
At a glance
CVE-2021-39327 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the BulletProof Security WordPress plugin, affecting versions <= 5.1. 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 5.2; sites on affected versions should update now. Disclosed September 2021, reported by Vincent Rakotomanga.
Vulnerability Overview
The BulletProof Security WordPress plugin is vulnerable to sensitive information disclosure due to a file path disclosure in the publicly accessible ~/db_backup_log.txt file which grants attackers the full path of the site, in addition to the path of database backup files. This affects versions up to, and including, 5.1.
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 BulletProof Security <= 5.1 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 BulletProof Security the fix is 5.2: builds <= 5.1 are affected, anything from 5.2 onward is not.
Remediation
Update to version 5.2, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: BulletProof Security 5.2 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in BulletProof Security
- 8.8CVE-2014-7959: BulletProof Security < .51.1 SQL Injection
CVE-2014-7959 - 7.2BulletProof Security <= .53.2 Cross-Site Scripting
- 6.4BulletProof Security <= .53.3 Cross-Site Scripting
- 6.1CVE-2022-1265: BulletProof Security <= 6.0 Stored Cross-Site Scripting
CVE-2022-1265 - 6.1CVE-2013-3487: BulletProof Security <= .48.9 Cross-Site Scripting
CVE-2013-3487 - 6.1CVE-2012-4268: BulletProof Security < .47.1 Reflected XSS
CVE-2012-4268 - 5.5CVE-2022-0590: BulletProof Security <= 5.7 Admin+ Stored XSS
CVE-2022-0590 - 5.4CVE-2014-7958: BulletProof Security < .51.1 Cross-Site Scripting
CVE-2014-7958
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C