sales@hackhalt.com

Home / Threats / CVE-2021-39327

Bulletproof Security - Information Disclosure (CVE-2021-39327)

CVE-2021-39327

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.

CVE-2021-39327

MEDIUM CVSS 5.3 Published 2021-09-17 Updated 2026-06-17
AI Risk Elevated (56/100) Active Exploit: No strong signal Published Exploit: Public exploit references found Priority: P3 Priority
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Affected Components 1
Reference Links 5
AI Risk Engine Elevated (56/100)
Exploitability Medium
Active Exploitation No strong signal
Published Exploit Status Public exploit references found

Threat Timeline

  1. 2021-09-17 CVE published and first recorded in the threat feed.
  2. 2026-06-17 Record updated with latest vulnerability metadata.
  3. 2026-04-12 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 224 days ago

AI enriched 224 days ago (2026-04-12 02:12 UTC)

Technical Summary

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.

Potential Impact

Severity is MEDIUM (CVSS 5.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Medium based on published exploit references.

Primary risk drivers: published exploit references

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 56/100 (Elevated, Medium) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Bulletproof Security PLUGIN · bulletproof-security Affected: <= 5.1 Fixed version not specified

References

What to do about this

Patch on your next cycle Worth fixing, but not ahead of other work.

Fix it

Update Bulletproof Security to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Restrict REST API in Hack Halt Pro blocks this class of attack before WordPress processes the request.

Require authentication for REST namespaces that do not need to be public, so the API cannot be used to enumerate content and accounts.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Bulletproof Security, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Bulletproof Security.

How do I fix it?

Update Bulletproof Security to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Restrict REST API in Hack Halt Pro contains this class of attack at the request layer.

What can an attacker actually do?

This is a Information Disclosure flaw. An attacker who exploits it can read data they were never meant to see, which is often the first step in a larger attack.