CVE-2024-6330·PHP vulnerability
The GEO my WP WordPress plugin before 4.5.0.2 does not prevent unauthenticated attackers from including arbitrary files in PHP's execution context, which leads to Remote Code Execution.
- Severity
- critical
- Software
- PHP
- Fixed in
- 4.5.0.2
- Published
- 2024-08-19
Affected versions
Until: 4.5.0.2
Fixed in: 4.5.0.2
How to fix this CVE
Update the GEO my WP WordPress plugin to version 4.5.0.2 or later immediately to patch the arbitrary file inclusion vulnerability that allows unauthenticated remote code execution. If you cannot update the plugin immediately, disable or remove it from your WordPress installation until the patch can be applied. Verify that PHP itself is running the latest security-patched version available for your distribution.
sudo dnf update phpDefensia detects this vulnerability
What an exploitation attempt looks like
Sample log line indicative of exploitation attempts:
GET|POST requests containing file inclusion payloads targeting plugin directory with parameters such as (?:file|include|path)=(?:\.\.\/|\.\.\\|%2e%2e%2f) or paths attempting to access /etc/passwd, wp-config.php, or other sensitive files; also look for POST requests with multipart form data attempting to upload executable files to plugin directoriesWAF 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 file traversal sequences (../, ..\, %2e%2e%2f, %252e) in query parameters and POST bodies targeting /wp-content/plugins/geo-my-wp/. Additionally, restrict execution permissions on plugin directories and disable dynamic PHP execution in upload directories.How to check if you are affected
- Run `php -v` to check the installed PHP version and ensure it is the latest patched release for your distribution.
- Check the GEO my WP plugin version by navigating to WordPress Admin > Plugins and locating 'GEO my WP'; verify the version is at least 4.5.0.2.
- Review web server access logs for suspicious file inclusion attempts targeting PHP scripts, looking for patterns like `?file=` or `?include=` parameters with paths outside the plugin directory (e.g., `GET /wp-content/plugins/geo-my-wp/ HTTP/1.1` followed by unusual parameter values).
- Confirm the fix by re-running `php -v` and re-checking the GEO my WP plugin version in WordPress to ensure it displays 4.5.0.2 or higher.
FAQ
What is CVE-2024-6330?
CVE-2024-6330 is a critical remote code execution flaw in the GEO my WP WordPress plugin (versions before 4.5.0.2) that allows unauthenticated attackers to load arbitrary PHP files into the web server's execution context, leading to full system compromise.
Is CVE-2024-6330 being actively exploited?
According to CISA's KEV catalog, CVE-2024-6330 is not currently listed as actively exploited in the wild, though the critical severity and ease of exploitation make prompt patching essential.
What versions of PHP are affected by CVE-2024-6330?
CVE-2024-6330 affects the GEO my WP WordPress plugin in all versions prior to 4.5.0.2; it is not a vulnerability in PHP itself but in the plugin's handling of file inclusion within PHP.
How do I check if my server is vulnerable to CVE-2024-6330?
In WordPress Admin, go to Plugins and check the GEO my WP version; if it shows any version below 4.5.0.2, your site is vulnerable. You can also inspect the plugin's readme.txt file in `/wp-content/plugins/geo-my-wp/` for the version number.
Does Defensia detect CVE-2024-6330?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the GEO my WP plugin is detected on a monitored WordPress site, CVE-2024-6330 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-6330. Free for 1 server.
Get started free