Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

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

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

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

Question 3

Who is affected? (Versions/Components)

Accepted Answer

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

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

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

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

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

Question 6

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

Accepted Answer

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

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

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

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

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

Question 9

What if no patch? (Workaround)

Accepted Answer

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

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

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

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

CVE-2020-36112 — AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

Q2Root Cause? (CWE/Flaw)

Q3Who is affected? (Versions/Components)

Q4What can hackers do? (Privileges/Data)

Q5Is exploitation threshold high? (Auth/Config)

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

Q7How to self-check? (Features/Scanning)

Q8Is it fixed officially? (Patch/Mitigation)

Q9What if no patch? (Workaround)

Q10Is it urgent? (Priority Suggestion)

Continue exploring