dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-6722

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The BitFire Security plugin for WordPress creates publicly accessible directories named bitfire_* that store sensitive files (config.ini, debug.log, etc.) without any access restrictions. When server directory listing is enabled and the wp-content/plugins/index.php file is missing or ignored, unauthenticated attackers can browse these directories and download sensitive configuration and log files.

MitigationImmediately restrict access to bitfire_* directories via .htaccess rules or server configuration to deny all HTTP requests, and ensure index.php files exist in all plugin subdirectories to prevent directory listing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if BitFire Security plugin is installed
    Inspect the wp-content/plugins/ directory for a folder named 'bitfire' or any folder starting with 'bitfire'. Use command: ls -la /path/to/wordpress/wp-content/plugins/ | grep -i bitfire
    Affected if BitFire plugin folder exists in wp-content/plugins/
  2. Locate bitfire_* directories created by the plugin
    Search for any directories matching the pattern bitfire_* within the WordPress installation, particularly under wp-content/. Use command: find /path/to/wordpress -type d -name 'bitfire*' 2>/dev/null
    Affected if Directories named bitfire_* exist in the wp-content directory or subdirectories
  3. Verify sensitive files exist in bitfire_* directories
    List contents of discovered bitfire_* directories. Look for files named config.ini, debug.log, or other configuration/log files. Use command: ls -la /path/to/wordpress/wp-content/bitfire*/
    Affected if Files such as config.ini, debug.log, or other sensitive configuration files are present in bitfire_* directories
  4. Check if directory listing is enabled on the server
    Attempt to access the bitfire_* directory via HTTP without an index file. Try accessing http://example.com/wp-content/bitfire_*/ (or the discovered directory name). If the server returns a directory listing showing file contents, listing is enabled.
    Affected if The server returns a directory listing (HTML page showing files) when accessing the bitfire_* directory directly, indicating directory listing is enabled and no index.php exists to block it
  5. Verify absence of index.php in plugin subdirectories
    Check if wp-content/plugins/index.php exists. Use command: ls -la /path/to/wordpress/wp-content/plugins/index.php. If it exists, also verify the server is not ignoring it via .htaccess or server configuration.
    Affected if wp-content/plugins/index.php is missing, or the server configuration is set to ignore it, allowing directory listing to proceed

You are affected if the BitFire plugin is installed, bitfire_* directories exist with sensitive files, and directory listing is enabled or the plugins/index.php file is missing, allowing unauthenticated access to those sensitive files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately restrict access to bitfire_* directories via .htaccess rules or server configuration to deny all HTTP requests, and ensure index.php files exist in all plugin subdirectories to prevent directory listing.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6722 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6722 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data