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-13539 Overview
CVE-2024-13539 is a Full Path Disclosure vulnerability in the AForms Eats plugin for WordPress, developed by vividcolorsjp. The flaw affects all versions up to and including 1.3.1. The issue stems from the publicly accessible /vendor/aura/payload-interface/phpunit.php file, which emits PHP error messages that expose the absolute filesystem path of the web application. Unauthenticated remote attackers can request this file to retrieve the server path. The disclosed information is not directly exploitable but can facilitate chained attacks that require knowledge of the webroot or application directory structure. This weakness is categorized under CWE-209: Generation of Error Message Containing Sensitive Information.
Critical Impact
Unauthenticated attackers can obtain the full server-side filesystem path of a WordPress installation, aiding reconnaissance for subsequent exploitation.
Affected Products
- AForms Eats plugin for WordPress (vividcolorsjp:aforms_eats)
- All versions up to and including 1.3.1
- WordPress sites bundling the vulnerable /vendor/aura/payload-interface/phpunit.php file
Discovery Timeline
- 2025-02-12 - CVE-2024-13539 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-13539
Vulnerability Analysis
The AForms Eats plugin ships a development artifact at /vendor/aura/payload-interface/phpunit.php within the plugin directory. This file is reachable over HTTP without authentication. When requested directly, the PHP interpreter attempts to execute the file outside its intended PHPUnit test context, generating fatal error messages that include the absolute path of the script on the server. Attackers performing basic reconnaissance against WordPress sites can issue a single HTTP GET request to this URL and parse the response for the disclosed path. The vulnerability does not grant code execution, data modification, or direct access to sensitive content on its own. However, the absolute path information supports exploitation of file-based vulnerabilities such as Local File Inclusion (LFI), Log Poisoning, or path-dependent injection flaws elsewhere in the stack. For technical details, see the Wordfence Vulnerability Report.
Root Cause
The root cause is a packaging and deployment issue. The aura/payload-interface Composer dependency includes a phpunit.php bootstrap file intended only for development and testing. The plugin distributes this file inside the vendor/ directory without an access restriction such as a web server rule, .htaccess deny directive, or in-script execution guard. Combined with verbose PHP error reporting that echoes absolute paths, the file becomes an information disclosure primitive.
Attack Vector
Exploitation requires a single unauthenticated HTTP request to the vulnerable path on a target WordPress site, for example GET /wp-content/plugins/aforms-eats/vendor/aura/payload-interface/phpunit.php. The response body contains PHP error output that reveals the absolute filesystem path. No user interaction, credentials, or elevated privileges are needed. See the WordPress PHPUnit File reference for the exact file in question.
No verified proof-of-concept code is published for this issue. The vulnerability is described in prose only, as it does not require a crafted payload beyond direct URL access.
Detection Methods for CVE-2024-13539
Indicators of Compromise
- HTTP requests to /wp-content/plugins/aforms-eats/vendor/aura/payload-interface/phpunit.php in web server access logs
- HTTP 200 responses containing PHP fatal error strings such as Fatal error: or in /var/www/...
- Repeated unauthenticated scans targeting /vendor/ subpaths across installed plugins
Detection Strategies
- Grep web access logs for the string payload-interface/phpunit.php against the plugin directory
- Alert on HTTP responses that return PHP error output containing absolute paths (/home/, /var/www/, /srv/)
- Monitor for scanner User-Agent strings issuing bulk requests to WordPress vendor/ directories
Monitoring Recommendations
- Enable WordPress-aware WAF signatures that block direct access to vendor/ directories within plugin paths
- Audit response bodies for leaked filesystem paths using DLP or outbound content inspection
- Track plugin inventory and version data across managed WordPress deployments to flag outdated AForms Eats installs
How to Mitigate CVE-2024-13539
Immediate Actions Required
- Update the AForms Eats plugin to a version later than 1.3.1 once the vendor publishes a patched release
- Block external access to /wp-content/plugins/aforms-eats/vendor/ at the web server or WAF layer
- Disable display_errors in production PHP configuration to prevent error output from reaching clients
- Audit all installed WordPress plugins for similarly exposed phpunit.php or test bootstrap files
Patch Information
The vendor committed changes referenced in the WordPress Changeset Log addressing the exposed file. Site administrators should update the plugin through the WordPress admin dashboard. Confirm the installed version is greater than 1.3.1 after update.
Workarounds
- Add an Apache or Nginx rule denying HTTP access to any */vendor/* path under wp-content/plugins/
- Delete the vendor/aura/payload-interface/phpunit.php file if it is not required at runtime
- Set display_errors = Off and log_errors = On in php.ini to suppress error output to HTTP responses
- Deploy a WordPress security plugin or WAF rule that blocks requests to development and test files
# Nginx configuration example to block direct access to vendor directories
location ~* /wp-content/plugins/.*/vendor/.*\.php$ {
deny all;
return 403;
}
# php.ini hardening to suppress path disclosure
# display_errors = Off
# log_errors = On
# error_log = /var/log/php/error.log
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

