CVE-2025-67919
📋 TL;DR
This vulnerability allows attackers to bypass authorization controls in Woffice Core by manipulating user-controlled keys, potentially accessing unauthorized data or functions. It affects all WordPress sites using Woffice Core plugin versions up to and including 5.4.30.
💻 Affected Systems
- Woffice 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
Attackers could access sensitive user data, modify critical settings, or perform administrative actions without proper authorization, potentially leading to data breach or site compromise.
Likely Case
Unauthorized access to user profiles, private content, or restricted functionality through IDOR (Insecure Direct Object Reference) attacks.
If Mitigated
Limited impact with proper access controls, input validation, and security monitoring in place.
🎯 Exploit Status
Exploitation requires some user access but is technically simple once initial access is obtained.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Versions after 5.4.30
Restart Required: No
Instructions:
1. Log into WordPress admin panel
2. Navigate to Plugins → Installed Plugins
3. Find Woffice Core plugin
4. Click 'Update Now' if update available
5. If no update available, download latest version from WordPress repository
6. Deactivate, delete old version, upload and activate new version
🔧 Temporary Workarounds
Temporary Access Restriction
allRestrict access to vulnerable endpoints using web application firewall or .htaccess rules
# Example .htaccess rule to restrict access to specific paths
RewriteCond %{REQUEST_URI} ^/wp-content/plugins/woffice-core/.*$
RewriteRule .* - [F,L]
🧯 If You Can't Patch
- Implement strict access control checks at application layer
- Deploy web application firewall with IDOR protection rules
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel → Plugins → Woffice Core version numberCheck Version:
wp plugin list --name=woffice-core --field=versionVerify Fix Applied:
Verify plugin version is greater than 5.4.30 and test authorization controls📡 Detection & Monitoring
Log Indicators:
- Unusual access patterns to user objects
- Failed authorization attempts followed by successful access
- Access to sequential object IDs
Network Indicators:
- HTTP requests with manipulated ID parameters
- Unusual API calls to user/object endpoints
SIEM Query:
source="web_logs" AND (uri_path="/wp-content/plugins/woffice-core/" OR user_agent CONTAINS "woffice") AND (status_code=200 OR status_code=403) | stats count by src_ip, uri_path