CVE-2024-6460·PHP vulnerability
The Grow by Tradedoubler WordPress plugin through 2.0.21 is vulnerable to Local File Inclusion via the component parameter. This makes it possible for attackers to include and execute PHP files on the server, allowing the execution of any PHP code in those files.
- Severity
- critical
- Software
- PHP
- Fixed in
- 2.0.22
- Published
- 2024-08-16
Affected versions
Until: 2.0.22
Fixed in: 2.0.22
How to fix this CVE
Update the Grow by Tradedoubler WordPress plugin to version 2.0.22 or later to eliminate the local file inclusion vulnerability in the component parameter. This patch prevents attackers from leveraging path traversal techniques to access and execute arbitrary PHP files on your server. Apply the update immediately through your WordPress plugin management interface or via command line.
sudo dnf update php php-common php-cliDefensia detects this vulnerability
What an exploitation attempt looks like
Sample log line indicative of exploitation attempts:
POST|GET /wp-admin/admin-ajax.php.*component=.*(\.\./|%2e%2e|php:|file:|phar:)WAF mitigation (if patching is not yet possible)
Add this rule to your WAF to block exploitation attempts while you schedule the patch.
Implement WAF rules to block requests containing the 'component' parameter with path traversal sequences (../, %2e%2e, encoded dots) or protocol handlers (file:, php:, phar:). Example: Block requests matching pattern: /wp-admin/admin-ajax.php.*component.*[./]{2,}|component.*(file:|php:|phar:)How to check if you are affected
- Check installed WordPress plugin version: grep 'Version:' /var/www/html/wp-content/plugins/grow-by-tradedoubler/grow-by-tradedoubler.php
- Verify the plugin's main file exists and examine it for vulnerable component parameter handling: find /var/www/html/wp-content/plugins/grow-by-tradedoubler -name '*.php' | head -1
- Search web server logs for exploitation attempts using the component parameter: grep -i 'component=' /var/log/apache2/access.log | grep -E '(\.\./|%2e%2e|php:|file:)'
- Confirm the plugin has been updated to 2.0.22 or later: curl -s https://api.wordpress.org/plugins/info/1.0/grow-by-tradedoubler.json | grep version
FAQ
What is CVE-2024-6460?
CVE-2024-6460 is a critical local file inclusion (LFI) vulnerability in the Grow by Tradedoubler WordPress plugin that allows remote attackers to execute arbitrary PHP code by manipulating the component parameter. The vulnerability has a CVSS score of 9.8, indicating severe impact on confidentiality, integrity, and availability.
Is CVE-2024-6460 being actively exploited?
Currently, CVE-2024-6460 is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploits are available. However, the critical severity and ease of exploitation mean deployment of version 2.0.22 should be treated as urgent.
What versions of the Grow by Tradedoubler plugin are affected by CVE-2024-6460?
All versions of the Grow by Tradedoubler WordPress plugin through version 2.0.21 are vulnerable. Version 2.0.22 and later contain the security fix.
How do I check if my server is vulnerable to CVE-2024-6460?
Run: grep 'Version:' /var/www/html/wp-content/plugins/grow-by-tradedoubler/grow-by-tradedoubler.php and compare the version number against 2.0.22. If the installed version is 2.0.21 or earlier, your site is vulnerable.
Does Defensia detect CVE-2024-6460?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Grow by Tradedoubler WordPress plugin is detected on a monitored server with version 2.0.21 or earlier, CVE-2024-6460 will appear in your dashboard with remediation steps.
Related PHP CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-6460. Free for 1 server.
Get started free