CVE-2025-14068
📋 TL;DR
The WPNakama WordPress plugin contains a time-based SQL injection vulnerability in the 'order_by' parameter that allows unauthenticated attackers to execute arbitrary SQL queries. This can lead to extraction of sensitive database information like user credentials, personal data, or configuration details. All WordPress sites using WPNakama plugin versions up to 0.6.3 are affected.
💻 Affected Systems
- WPNakama 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
Complete database compromise including extraction of administrator credentials, user personal information, and sensitive site configuration data, potentially leading to full site takeover.
Likely Case
Data exfiltration of user information, plugin settings, and potentially WordPress configuration details that could enable further attacks.
If Mitigated
Limited information disclosure if database permissions are properly restricted and sensitive data is encrypted.
🎯 Exploit Status
Time-based SQL injection requires no authentication and can be automated with readily available tools.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 0.6.4 or later
Vendor Advisory: https://wordpress.org/plugins/wpnakama/
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find WPNakama plugin. 4. Click 'Update Now' if update is available. 5. If no update appears, manually download version 0.6.4+ from WordPress.org and replace plugin files.
🔧 Temporary Workarounds
Disable WPNakama Plugin
allTemporarily disable the vulnerable plugin until patched
wp plugin deactivate wpnakama
Web Application Firewall Rule
allBlock SQL injection patterns targeting the order_by parameter
Add WAF rule to block requests containing SQL injection patterns in order_by parameter
🧯 If You Can't Patch
- Implement strict input validation and parameterized queries at application level
- Restrict database user permissions to read-only for the WPNakama plugin database user
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin panel → Plugins → Installed Plugins for WPNakama version ≤ 0.6.3Check Version:
wp plugin get wpnakama --field=versionVerify Fix Applied:
Verify WPNakama plugin version is 0.6.4 or higher in WordPress admin panel📡 Detection & Monitoring
Log Indicators:
- Unusual SQL queries in database logs
- Multiple requests with order_by parameter containing SQL keywords
- Long response times from WPNakama endpoints
Network Indicators:
- HTTP requests with SQL injection patterns in order_by parameter
- Repeated requests to WPNakama API endpoints with varying order_by values
SIEM Query:
source="web_server" AND uri="*wpnakama*" AND (order_by="*sleep*" OR order_by="*benchmark*" OR order_by="*waitfor*" OR order_by="*pg_sleep*")🔗 References
- https://cwe.mitre.org/data/definitions/89.html
- https://plugins.trac.wordpress.org/browser/wpnakama/tags/0.6.3/inc/class-wpnakama-api.php#L206
- https://plugins.trac.wordpress.org/browser/wpnakama/tags/0.6.3/inc/class-wpnakama.php#L197
- https://plugins.trac.wordpress.org/browser/wpnakama/trunk/inc/class-wpnakama-api.php#L206
- https://plugins.trac.wordpress.org/browser/wpnakama/trunk/inc/class-wpnakama.php#L197
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3412904%40wpnakama&new=3412904%40wpnakama&sfp_email=&sfph_mail=
- https://www.wordfence.com/threat-intel/vulnerabilities/id/9abfd0f5-f665-4745-9756-8445ddbdc29d?source=cve
