CVE-2025-64377
📋 TL;DR
This vulnerability allows attackers to include local files on the server through improper input validation in PHP include/require statements. It affects WordPress ListingPro theme users running versions below 2.9.10, potentially leading to sensitive information disclosure or code execution.
💻 Affected Systems
- CridioStudio ListingPro WordPress Theme
⚠️ 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 local file inclusion leading to remote code execution, sensitive file access (like /etc/passwd, configuration files), and complete system takeover.
Likely Case
Information disclosure of sensitive server files, configuration exposure, and potential privilege escalation through reading credential files.
If Mitigated
Limited impact with proper file permissions, web server restrictions, and PHP security settings preventing file inclusion outside web root.
🎯 Exploit Status
Simple HTTP requests with crafted parameters can trigger the vulnerability. Public exploit details available on security research sites.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 2.9.10
Vendor Advisory: https://patchstack.com/database/Wordpress/Theme/listingpro/vulnerability/wordpress-listingpro-theme-2-9-10-local-file-inclusion-vulnerability?_s_id=cve
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Appearance > Themes. 3. Check if ListingPro theme is active. 4. Update to version 2.9.10 via WordPress updates or manual upload. 5. Clear cache if using caching plugins.
🔧 Temporary Workarounds
Disable vulnerable functionality
allTemporarily disable or remove the vulnerable component until patching
# Identify vulnerable files via patch diff and comment out/include validation
Web Application Firewall rule
allBlock requests containing local file inclusion patterns
# WAF rule to block ../ patterns and file:// URIs in requests
🧯 If You Can't Patch
- Implement strict input validation and sanitization for all user-controlled file paths
- Restrict PHP file inclusion functions via disable_functions in php.ini or web server configuration
🔍 How to Verify
Check if Vulnerable:
Check WordPress theme version in wp-content/themes/listingpro/style.css or via WordPress admin > Appearance > ThemesCheck Version:
grep 'Version' wp-content/themes/listingpro/style.css | head -1Verify Fix Applied:
Confirm theme version is 2.9.10 or higher and test vulnerable endpoints with safe payloads📡 Detection & Monitoring
Log Indicators:
- HTTP requests with ../ sequences, file:// URIs, or unusual file paths in parameters
- PHP warnings about failed file inclusions
Network Indicators:
- Unusual file path patterns in HTTP GET/POST parameters
- Requests to sensitive server files via web parameters
SIEM Query:
web.url:*../* OR web.uri:*file://* OR web.param:*etc/passwd*