CVE-2025-69375
📋 TL;DR
This CVE describes a PHP Local File Inclusion vulnerability in the SolverWp Portfolio Builder WordPress plugin. Attackers can exploit improper filename control in include/require statements to read sensitive files on the server. WordPress sites using Portfolio Builder version 1.2.5 or earlier are affected.
💻 Affected Systems
- SolverWp Portfolio Builder 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 /etc/passwd, database credentials, or session files, potentially leading to remote code execution.
Likely Case
Information disclosure of sensitive server files, configuration files, or source code.
If Mitigated
No impact if proper file permissions and web server configurations prevent directory traversal.
🎯 Exploit Status
Simple path traversal techniques can exploit this vulnerability without authentication.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Version after 1.2.5
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins. 3. Find 'Portfolio Builder'. 4. Click 'Update Now' if update available. 5. If no update, deactivate and delete plugin.
🔧 Temporary Workarounds
Disable vulnerable plugin
allDeactivate the Portfolio Builder plugin until patched version is available
wp plugin deactivate swp-portfolio
Web server file restriction
linuxConfigure web server to restrict access to sensitive directories
# In Apache .htaccess: Options -Indexes
# In Nginx: location ~ /\. { deny all; }
🧯 If You Can't Patch
- Implement web application firewall (WAF) rules to block LFI patterns
- Restrict file permissions and disable PHP execution in upload directories
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel > Plugins > Portfolio Builder version. If version is 1.2.5 or lower, you are vulnerable.Check Version:
wp plugin get swp-portfolio --field=versionVerify Fix Applied:
Verify plugin version is higher than 1.2.5 in WordPress admin panel.📡 Detection & Monitoring
Log Indicators:
- Unusual file path requests in access logs containing '../' sequences
- Requests to Portfolio Builder plugin files with suspicious parameters
Network Indicators:
- HTTP requests with path traversal sequences in URL parameters
SIEM Query:
source="web_access_logs" AND (uri="*../*" OR uri="*swp-portfolio*")