Strategic Overview
- Status
- Patched in .51.1
- Affected Plugin
- BulletProof Security
- Affected Version
< .51.1- CVSS
- 8.8High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2014-7959
At a glance
CVE-2014-7959 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the BulletProof Security WordPress plugin, affecting versions < .51.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version .51.1; sites on affected versions should update now. Disclosed October 2014, reported by Pietro Oliva.
Vulnerability Overview
SQL injection vulnerability in admin/htaccess/bpsunlock.php in the BulletProof Security plugin before .51.1 for WordPress allows remote authenticated users to execute arbitrary SQL commands via the tableprefix parameter.
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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in BulletProof Security < .51.1 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For BulletProof Security the fix is .51.1: builds < .51.1 are affected, anything from .51.1 onward is not.
Remediation
Update to version .51.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to BulletProof Security: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: BulletProof Security .51.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in BulletProof Security
- 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 - 5.3CVE-2025-67931: BulletProof Security <= 6.9 Info Exposure
CVE-2025-67931
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C