CVE-2025-28947
📋 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 MBStore - Digital WooCommerce WordPress Theme version 2.3 and earlier. Attackers can potentially read sensitive files or execute arbitrary code.
💻 Affected Systems
- MBStore - Digital WooCommerce 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
Remote code execution leading to complete server compromise, data theft, and website defacement.
Likely Case
Local file inclusion allowing reading of sensitive configuration files (wp-config.php), database credentials, and potentially limited code execution.
If Mitigated
Limited impact if file permissions are restrictive and web server runs with minimal privileges.
🎯 Exploit Status
PHP local file inclusion vulnerabilities are well-understood and often weaponized quickly.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Version after 2.3
Restart Required: No
Instructions:
1. Update the MBStore theme to the latest version via WordPress admin panel. 2. If update not available, remove the theme entirely and replace with a secure alternative.
🔧 Temporary Workarounds
Disable vulnerable theme
allSwitch to a different WordPress theme and deactivate/remove MBStore theme
Restrict PHP file operations
linuxConfigure PHP to disable dangerous functions and restrict file inclusion paths
php.ini: open_basedir = /var/www/html
php.ini: disable_functions = include,require,include_once,require_once
🧯 If You Can't Patch
- Implement web application firewall (WAF) rules to block file inclusion patterns
- Restrict file permissions and run web server with minimal privileges
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel > Appearance > Themes for MBStore theme version 2.3 or earlierCheck Version:
Check wp-content/themes/mbstore/style.css for Version: headerVerify Fix Applied:
Verify theme version is updated beyond 2.3 or theme is completely removed📡 Detection & Monitoring
Log Indicators:
- Unusual file paths in PHP error logs
- Multiple include/require attempts with directory traversal patterns
- Access to wp-config.php or other sensitive files
Network Indicators:
- HTTP requests with file inclusion parameters (include=, require=, file=)
- Requests containing directory traversal sequences (../)
SIEM Query:
web.url:*include=* OR web.url:*require=* OR web.url:*file=* AND web.url:*../*