The BulletProof Security WordPress plugin through 7.2 does not sufficiently protect its security log files or prevent
Source GCVE Database
Not known to be exploited.
Data as of 10 Nov 2026, 07:18 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| BulletProof Security | Affected
| Fixed in– |
AI-suggested
Until a fix is available, administrators should review their web-server configurations to ensure that access controls effectively restrict access to security log files and consider additional protective measures such as moving logs outside the web root or restricting file permissions.
Description
The BulletProof Security WordPress plugin versions through 7.2 have insufficient protection for their security log files. This vulnerability allows unauthenticated attackers to read sensitive logged request data, including authentication material, due to reliance on access controls that are not enforced under all common web-server configurations.