This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis β
Q1What is this vulnerability? (Essence + Consequences)
π¨ **Essence**: SPIP `referer_spam` plugin (v1.3.0-) suffers from **SQL Injection**.β¦
π‘οΈ **Root Cause**: **CWE-89** (SQL Injection). <br>π **Flaw**: The `referer_spam_ajouter` and `referer_spam_supprimer` handlers fail to validate/sanitize the `url` parameter before inserting it into SQL queries.
Q3Who is affected? (Versions/Components)
π’ **Affected**: **SPIP** CMS users running the `referer_spam` extension. <br>π¦ **Version**: Versions **prior to 1.3.0** are vulnerable. Newer versions are safe.
Q4What can hackers do? (Privileges/Data)
π **Attacker Capabilities**: <br>π **Privileges**: Unauthenticated access required. <br>π **Data**: High risk of **Confidentiality, Integrity, and Availability** loss. Can read/modify/delete database records.
π’ **Public Exploit**: **Yes**. <br>π References include technical descriptions and exploit details from `chocapikk.com` and `vulncheck.com`. Wild exploitation is possible.
Q7How to self-check? (Features/Scanning)
π **Self-Check**: <br>1. Check if `referer_spam` plugin is installed. <br>2. Verify version is **< 1.3.0**. <br>3. Scan for SQL injection in `url` parameters of `referer_spam_ajouter/supprimer` endpoints.
Q8Is it fixed officially? (Patch/Mitigation)
β **Official Fix**: **Yes**. <br>π§ **Patch**: Version **1.3.0** and above fix the issue. See the SPIP Git commit `33682df` for the patch details.
Q9What if no patch? (Workaround)
π§ **No Patch Workaround**: <br>1. **Disable** the `referer_spam` plugin immediately. <br>2. **WAF**: Block SQL injection patterns in `url` parameters. <br>3.β¦
π₯ **Urgency**: **CRITICAL**. <br>β±οΈ **Priority**: **Immediate Action**. CVSS 9.8 + Unauthenticated + Public Exploit = High risk of active exploitation. Patch or disable NOW.