CVE-2025-64284
📋 TL;DR
This CVE describes a PHP Local File Inclusion vulnerability in the Majestic Support WordPress plugin. Attackers can include arbitrary local files, potentially leading to sensitive information disclosure or remote code execution. WordPress sites using vulnerable versions of the Majestic Support plugin are affected.
💻 Affected Systems
- Majestic Support 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
Remote code execution leading to complete system compromise, data exfiltration, or website defacement.
Likely Case
Sensitive file disclosure (configuration files, database credentials) or limited code execution within web server context.
If Mitigated
No impact if proper file permissions and web server hardening are implemented.
🎯 Exploit Status
Simple HTTP requests can trigger the vulnerability without authentication.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 1.1.2 or later
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins. 3. Find Majestic Support. 4. Click 'Update Now' or manually update to version 1.1.2+. 5. Verify update completed successfully.
🔧 Temporary Workarounds
Disable Plugin
allTemporarily disable the vulnerable plugin until patched.
wp plugin deactivate majestic-support
Web Application Firewall Rule
allBlock requests containing file inclusion patterns.
ModSecurity rule: SecRule ARGS "\.\./" "id:1001,phase:2,deny,msg:'Path Traversal Attempt'"
WAF rule to block requests with 'include' or 'require' parameters
🧯 If You Can't Patch
- Remove the Majestic Support plugin entirely from production systems.
- Implement strict file permissions (644 for files, 755 for directories) and disable PHP execution in upload directories.
🔍 How to Verify
Check if Vulnerable:
Check WordPress plugin version via admin panel or inspect wp-content/plugins/majestic-support/readme.txt for version <=1.1.1.Check Version:
wp plugin get majestic-support --field=versionVerify Fix Applied:
Confirm plugin version is 1.1.2 or higher in WordPress admin or via readme.txt file.📡 Detection & Monitoring
Log Indicators:
- HTTP requests with parameters containing 'include', 'require', or path traversal sequences (../)
- Unusual file access patterns in web server logs
- PHP errors related to file inclusion failures
Network Indicators:
- HTTP GET/POST requests with file paths in parameters
- Traffic spikes to vulnerable plugin endpoints
SIEM Query:
source="web_server_logs" AND (uri="*majestic-support*" AND (param="*include*" OR param="*require*" OR param="*../*"))