CVE-2025-67957
📋 TL;DR
This vulnerability allows attackers to include local files on the server through improper filename control in PHP include/require statements. It affects WordPress sites using the Listivo Core plugin, potentially leading to sensitive file disclosure or code execution.
💻 Affected Systems
- TangibleWP Listivo Core 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 local file inclusion leading to remote code execution, sensitive data exposure, and complete site takeover.
Likely Case
Sensitive file disclosure (configuration files, database credentials), limited code execution, and potential privilege escalation.
If Mitigated
Limited impact with proper file permissions, web application firewalls, and restricted PHP configurations.
🎯 Exploit Status
Simple HTTP requests can trigger the vulnerability. Public exploit details available on security research sites.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 2.3.78 or later
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find Listivo Core and update to version 2.3.78+. 4. Verify update completes successfully.
🔧 Temporary Workarounds
Disable Listivo Core plugin
allTemporarily disable the vulnerable plugin until patched
wp plugin deactivate listivo-core
Restrict PHP file functions
linuxModify php.ini to disable dangerous functions
disable_functions = allow_url_include,allow_url_fopen
🧯 If You Can't Patch
- Implement web application firewall (WAF) rules to block file inclusion patterns
- Restrict file permissions and implement strict directory traversal protections
🔍 How to Verify
Check if Vulnerable:
Check WordPress plugin version via admin panel or wp-cli: wp plugin get listivo-core --field=versionCheck Version:
wp plugin get listivo-core --field=versionVerify Fix Applied:
Confirm version is 2.3.78 or higher and test file inclusion attempts return errors📡 Detection & Monitoring
Log Indicators:
- Unusual file paths in PHP error logs
- Multiple requests with ../ patterns
- Requests to plugin files with file parameter
Network Indicators:
- HTTP requests containing file inclusion patterns (../../etc/passwd)
- Abnormal requests to wp-content/plugins/listivo-core/
SIEM Query:
source="web_logs" AND (uri="*listivo-core*" AND (query="*file=*" OR query="*include=*" OR query="*../*"))