CVE-2025-0969
📋 TL;DR
The Brizy Page Builder WordPress plugin exposes administrator email addresses and password hashes to authenticated users with Contributor-level access or higher. This vulnerability allows attackers with basic WordPress accounts to harvest sensitive credentials that could lead to privilege escalation. All WordPress sites using Brizy Page Builder versions up to 2.7.16 are affected.
💻 Affected Systems
- Brizy - Page 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
Attackers obtain administrator password hashes, crack weak passwords, gain full administrative access to WordPress, install backdoors, deface websites, or steal sensitive data.
Likely Case
Attackers harvest administrator email addresses for phishing campaigns and attempt to crack weak password hashes to gain administrative access.
If Mitigated
With strong administrator passwords and proper access controls, attackers cannot crack hashes but still obtain email addresses for targeted attacks.
🎯 Exploit Status
Exploitation requires authenticated WordPress user with at least Contributor privileges. The vulnerability is in a public API endpoint.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 2.7.17
Vendor Advisory: https://wordpress.org/plugins/brizy/#developers
Restart Required: No
Instructions:
1. Log into WordPress admin panel
2. Navigate to Plugins → Installed Plugins
3. Find Brizy Page Builder
4. Click 'Update Now' if available
5. Or manually download version 2.7.17+ from WordPress plugin repository
6. Upload and replace existing plugin files
🔧 Temporary Workarounds
Disable Brizy Plugin
allTemporarily deactivate the Brizy plugin until patched
wp plugin deactivate brizy
Restrict User Registration
allDisable new user registration or require administrator approval for all new accounts
🧯 If You Can't Patch
- Implement strict access controls and monitor for suspicious user activity
- Use web application firewall rules to block access to the vulnerable API endpoint
🔍 How to Verify
Check if Vulnerable:
Check Brizy plugin version in WordPress admin panel under Plugins → Installed PluginsCheck Version:
wp plugin get brizy --field=versionVerify Fix Applied:
Confirm Brizy plugin version is 2.7.17 or higher in WordPress admin📡 Detection & Monitoring
Log Indicators:
- Unusual API calls to /wp-json/brizy/v1/users endpoint from non-admin users
- Multiple failed login attempts targeting administrator accounts
Network Indicators:
- HTTP POST requests to vulnerable API endpoint from authenticated users
SIEM Query:
source="wordpress.log" AND (uri_path="/wp-json/brizy/v1/users" OR plugin_version="brizy 2.7.16")