# CVE-2025-6722: BitFire <= 4.5 - Unauthenticated Information Exposure

> Unauthenticated attackers can read sensitive files like config.ini and debug.log if directory listing is enabled and index.php is missing.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Aug 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-fv5p-jgq7-gfm9

## What is CVE-2025-6722?

CVE-2025-6722 is a medium-severity vulnerability in bitslip6 BitFire Security – Firewall, WAF, Bot/Spam Blocker, Login Security, published on 2 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The BitFire Security – Firewall, WAF, Bot/Spam Blocker, Login Security plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.5 via the bitfire_* directory that automatically gets created and stores potentially sensitive files without any access restrictions. This makes it possible for unauthenticated attackers to extract sensitive data from various files like config.ini, debug.log, and more when directory listing is enabled on the server and the ~/wp-content/plugins/index.php file is missing or ignored.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-6722?


## How do I fix CVE-2025-6722?

No fix has been published for CVE-2025-6722 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-6722 being exploited?

There is no known exploitation of CVE-2025-6722 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6722 and fix it if it is affected.

What it is: CVE-2025-6722 is a medium-severity vulnerability in bitslip6 BitFire Security – Firewall, WAF, Bot/Spam Blocker, Login Security, published on 2 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6722 in the wild and no public exploit code.

Affected product: bitslip6 BitFire Security – Firewall, WAF, Bot/Spam Blocker, Login Security. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-6722/ (Markdown: https://insights.sbomify.com/CVE-2025-6722/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6722
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6722
- OSV: https://osv.dev/vulnerability/CVE-2025-6722

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-6722/
Summaries are generated and may contain mistakes; the official description above is the record.