Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-6554 Overview
CVE-2024-6554 affects the Branda – White Label WordPress, Custom Login Page Customizer plugin developed by wpmudev. All versions up to and including 3.4.18 are vulnerable to Full Path Disclosure. The plugin bundles Composer files without restricting direct HTTP access, allowing unauthenticated attackers to trigger errors that reveal the absolute filesystem path of the web application. This information supports reconnaissance for follow-on attacks but has limited standalone impact. The vulnerability is tracked under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Critical Impact
Unauthenticated remote attackers can retrieve the absolute server path of WordPress installations running vulnerable Branda plugin versions, aiding chained exploitation.
Affected Products
- Branda – White Label WordPress, Custom Login Page Customizer plugin versions <= 3.4.18
- WordPress installations with the wpmudev Branda plugin activated
- Sites using the bundled Composer dependency files in misc/composer/
Discovery Timeline
- 2024-07-11 - CVE-2024-6554 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-6554
Vulnerability Analysis
The Branda plugin ships a Composer-based prefix fixer script located at misc/composer/prefix-fixer.php. The plugin does not prevent direct HTTP access to these auxiliary files. When an unauthenticated request reaches this endpoint, PHP triggers runtime errors or notices that include the absolute filesystem path in the response. Attackers can use the disclosed path to refine payloads for other vulnerabilities such as Local File Inclusion, arbitrary file writes, or log poisoning. The issue is classified as an Information Disclosure vulnerability requiring no authentication or user interaction.
Root Cause
The root cause is missing access control on files under the plugin's misc/composer/ directory. Composer scripts and helpers are development-time utilities and should not be reachable over HTTP in production deployments. Because the plugin distributes these files inside the WordPress wp-content/plugins/branda-white-labeling/ directory, they are served directly by the web server. Direct invocation produces PHP output that includes the full server path of the application.
Attack Vector
An unauthenticated attacker sends an HTTP GET request to the exposed Composer helper file over the network. The web server executes the PHP script outside its intended context, and PHP returns errors containing the absolute directory path. No credentials, browser interaction, or elevated privileges are required. The disclosed path becomes a building block for subsequent attacks that require knowledge of on-disk locations. Further technical background is available in the Wordfence Vulnerability Analysis and the WordPress Plugin Prefix Fixer source.
Detection Methods for CVE-2024-6554
Indicators of Compromise
- HTTP GET requests to URIs containing /wp-content/plugins/branda-white-labeling/misc/composer/prefix-fixer.php
- Web server responses containing absolute filesystem paths such as /var/www/html/ or /home/<user>/public_html/
- Unusual anonymous access patterns to plugin subdirectories not linked from the site
Detection Strategies
- Inspect web server access logs for direct requests to files under wp-content/plugins/branda-white-labeling/misc/
- Deploy WAF rules that flag responses containing PHP error strings such as Fatal error, Warning:, or Stack trace: combined with filesystem paths
- Use vulnerability scanners with signatures for [CWE-200] Full Path Disclosure in WordPress plugin directories
Monitoring Recommendations
- Alert on repeated 200-status responses to auxiliary plugin files from single source IPs
- Monitor for reconnaissance patterns pairing plugin enumeration with subsequent targeted requests
- Track installed plugin versions and correlate wpmudev Branda instances at or below 3.4.18 against active scanning activity
How to Mitigate CVE-2024-6554
Immediate Actions Required
- Update the Branda plugin to a version above 3.4.18 where direct access to Composer files is blocked
- Audit all WordPress installations for the presence of the wpmudev Branda plugin and confirm current version
- Deploy web server rules that deny HTTP access to misc/composer/ paths within the plugin directory
Patch Information
The vendor addressed the issue in the plugin repository. Refer to the WordPress Changeset History for the fix commit. Upgrade to the latest available release of the Branda plugin through the WordPress plugin manager to receive the patched files.
Workarounds
- Add Apache or Nginx rules to deny requests matching wp-content/plugins/branda-white-labeling/misc/composer/*
- Disable PHP error display in production by setting display_errors = Off in php.ini
- Temporarily deactivate the Branda plugin until the update can be applied
# Nginx configuration to block direct access to plugin Composer files
location ~* /wp-content/plugins/branda-white-labeling/misc/composer/ {
deny all;
return 403;
}
# php.ini hardening to suppress path disclosure via error output
# display_errors = Off
# log_errors = On
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

