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

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2020-36112 — AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: SQL Injection in **Projectworlds Online Book Store** (PHP). <br>💥 **Consequences**: Attackers can **dump the entire database** running the web app. Critical data loss risk!

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **SQL Injection** flaw. Specifically in the `pubid` parameter within `bookPerPub.php`. <br>🔍 **Type**: Time-based blind, Boolean-based blind, and OR error-based injection.

Q3Who is affected? (Versions/Components)

👥 **Affected**: **Projectworlds Online Book Store Project In Php** version **1.0**. <br>📦 **Vendor**: Projectworlds (Austria). <br>⚠️ **Note**: Only v1.0 is confirmed vulnerable.

Q4What can hackers do? (Privileges/Data)

🕵️ **Attacker Capabilities**: <br>1️⃣ **Dump Database**: Extract all tables/data. <br>2️⃣ **Privileges**: Depends on DB user rights, but full data exposure is guaranteed.…

Q5Is exploitation threshold high? (Auth/Config)

🔓 **Exploitation Threshold**: **LOW**. <br>✅ **Auth**: No authentication required mentioned. <br>✅ **Config**: Direct parameter manipulation in `bookPerPub.php`. <br>🎯 **Ease**: Simple parameter injection via `pubid`.

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

💣 **Public Exploit**: **YES**. <br>🔗 **Source**: Exploit-DB ID **49314**. <br>🤖 **Automation**: Nuclei templates available for scanning. <br>⚡ **Status**: Wildly exploitable via standard SQLi techniques.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: <br>1️⃣ Scan for `bookPerPub.php` with `pubid` parameter. <br>2️⃣ Use **Nuclei** templates (CVE-2020-36112.yaml). <br>3️⃣ Test for **Time-based** or **Boolean-based** blind responses.…

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Official Fix**: **UNKNOWN** from provided data. <br>📅 **Published**: Jan 4, 2021. <br>⚠️ **Action**: Since no patch link is provided, assume **NO official patch** exists or is unavailable. Treat as unpatched.

Q9What if no patch? (Workaround)

🛡️ **Workaround**: <br>1️⃣ **Input Validation**: Sanitize `pubid` parameter strictly. <br>2️⃣ **WAF**: Block SQL keywords in `pubid`. <br>3️⃣ **Access Control**: Restrict access to `bookPerPub.php` if possible.…

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. <br>📉 **Priority**: **P1**. <br>💡 **Reason**: Full database dump is possible with low effort. No patch available. Immediate mitigation required to prevent data breach!