Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2025-9209 — AI Deep Analysis Summary

CVSS 9.8 · Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Unauthenticated Information Exposure via REST API. <br>💥 **Consequences**: Attackers can forge JWT tokens to bypass authentication. This leads to full account takeover, including admin privileges.…

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: CWE-200 (Information Exposure). <br>🔍 **Flaw**: The `/wp-json/wp/v2/users` endpoint exposes user private tokens and API keys.…

Q3Who is affected? (Versions/Components)

🏢 **Vendor**: Magnigenie. <br>📦 **Product**: RestroPress – Online Food Ordering System (WordPress Plugin). <br>📅 **Affected Versions**: 3.0.0 through 3.1.9.2.

Q4What can hackers do? (Privileges/Data)

🕵️ **Attacker Actions**: <br>1. Extract private tokens & API data. <br>2. Forge valid JWT tokens. <br>3. Authenticate as **any user**, including **Administrators**. <br>4. Gain full control over the food ordering system.

Q5Is exploitation threshold high? (Auth/Config)

📉 **Threshold**: VERY LOW. <br>✅ **Auth Required**: None. <br>🌐 **Access**: Publicly accessible via REST API. <br>⚙️ **Config**: No special configuration needed. Just a standard vulnerable installation.

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

💣 **Public Exploit**: YES. <br>🔗 **PoC Available**: <br>- GitHub: `Nxploited/CVE-2025-9209` (Mass automatic exploit tool). <br>- Nuclei Template: `projectdiscovery/nuclei-templates` (Automated scanning).…

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: <br>1. Scan for `/wp-json/wp/v2/users` endpoint. <br>2. Use Nuclei template for CVE-2025-9209. <br>3. Check if private tokens/API keys are exposed in the JSON response without authentication. <br>4.…

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Official Fix**: The data implies a fix exists (versions > 3.1.9.2 are safe). <br>📢 **Action**: Update RestroPress plugin to the latest version immediately.…

Q9What if no patch? (Workaround)

🛑 **No Patch Workaround**: <br>1. **Block Access**: Restrict `/wp-json/wp/v2/users` via WAF or firewall. <br>2. **Disable REST**: Limit REST API access if possible. <br>3.…

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: CRITICAL (CVSS 9.8). <br>⚡ **Priority**: IMMEDIATE ACTION REQUIRED. <br>📉 **Risk**: Unauthenticated, full admin takeover. <br>🚀 **Recommendation**: Patch NOW. Do not wait.