CVE-2024-47351
📋 TL;DR
This path traversal vulnerability in the MaxSlider WordPress plugin allows attackers to read arbitrary files on the server by manipulating file paths. It affects all WordPress sites running MaxSlider version 1.2.3 or earlier. Attackers can potentially access sensitive configuration files and other restricted data.
💻 Affected Systems
- MaxSlider WordPress Plugin
⚠️ Manual Verification Required
This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.
Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).
🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Full server compromise through reading sensitive files like wp-config.php containing database credentials, leading to database takeover and potential remote code execution.
Likely Case
Information disclosure of sensitive files including configuration files, source code, and potentially user data stored in accessible directories.
If Mitigated
Limited impact if proper file permissions restrict access to sensitive files and web server configurations prevent directory traversal.
🎯 Exploit Status
Simple path traversal attacks using directory traversal sequences like ../ to access files outside web root. Public exploit details available in security advisories.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 1.2.4 or later
Vendor Advisory: https://patchstack.com/database/vulnerability/maxslider/wordpress-maxslider-plugin-1-2-3-local-file-inclusion-vulnerability?_s_id=cve
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find MaxSlider and click 'Update Now'. 4. Verify update to version 1.2.4 or later. 5. Clear any caching plugins or CDN caches.
🔧 Temporary Workarounds
Disable MaxSlider Plugin
allTemporarily disable the vulnerable plugin until patching is possible
wp plugin deactivate maxslider
Web Server Path Restriction
linuxConfigure web server to block directory traversal attempts
# For Apache: Add to .htaccess
RewriteCond %{REQUEST_URI} \.\. [NC]
RewriteRule .* - [F,L]
🧯 If You Can't Patch
- Remove MaxSlider plugin completely from WordPress installation
- Implement web application firewall (WAF) rules to block path traversal patterns
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel → Plugins → MaxSlider version. If version is 1.2.3 or earlier, system is vulnerable.Check Version:
wp plugin get maxslider --field=versionVerify Fix Applied:
Verify MaxSlider plugin version is 1.2.4 or later in WordPress admin panel. Test with known path traversal payloads to confirm fix.📡 Detection & Monitoring
Log Indicators:
- HTTP requests containing ../ sequences
- Requests to MaxSlider endpoints with unusual file paths
- 403/404 errors for attempted file accesses outside web root
Network Indicators:
- HTTP requests with path traversal payloads to /wp-content/plugins/maxslider/ endpoints
SIEM Query:
source="web_logs" AND (uri="*../*" OR uri="*..%2f*") AND uri="*/maxslider/*"