Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2025-32603 β€” AI Deep Analysis Summary

CVSS 9.3 Β· Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Blind SQL Injection in 'WP Online Users Stats' plugin.…

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: **CWE-89** (SQL Injection). The flaw lies in the **improper handling of special elements** within SQL commands, allowing malicious input to alter query logic.

Q3Who is affected? (Versions/Components)

πŸ“¦ **Affected**: **WordPress Plugin: WP Online Users Stats**. πŸ“‰ **Version**: **1.0.0 and earlier**. 🏒 **Vendor**: HK-based developer.

Q4What can hackers do? (Privileges/Data)

πŸ•΅οΈ **Attacker Capabilities**: Due to **Blind SQLi**, hackers can infer data from the database. πŸ“Š **Impact**: High Confidentiality (C:H), Low Availability (A:L).…

Q5Is exploitation threshold high? (Auth/Config)

⚑ **Exploitation Threshold**: **LOW**. 🌐 **Network**: Remote (AV:N). πŸ”“ **Auth**: None required (PR:N, UI:N). 🎯 **Complexity**: Low (AC:L). This is a critical, easy-to-exploit vector.

Q6Is there a public Exp? (PoC/Wild Exploitation)

πŸ” **Public Exploit**: **No PoC provided** in the data. However, references point to Patchstack DB.…

Q7How to self-check? (Features/Scanning)

πŸ”Ž **Self-Check**: Scan for **WP Online Users Stats v1.0.0**. πŸ› οΈ **Method**: Look for SQL injection points in user statistics endpoints. Use automated scanners targeting CWE-89 on WordPress plugins.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Official Fix**: **Yes**. Update to the latest version. πŸ“ **Reference**: Patchstack database entry confirms the vulnerability and implies a patch exists for versions > 1.0.0.

Q9What if no patch? (Workaround)

🚧 **No Patch Workaround**: **Disable the plugin** immediately. 🚫 **Action**: Deactivate 'WP Online Users Stats' if you are on v1.0.0 or older. Remove it if not essential to avoid the attack surface.

Q10Is it urgent? (Priority Suggestion)

πŸ”₯ **Urgency**: **CRITICAL**. 🚨 **Priority**: **P1**. With **CVSS 3.1** (High Impact, Low Effort, No Auth), this requires **immediate patching or plugin removal** to prevent data breaches.