Q: Is it fixed officially? (Patch/Mitigation)

🩹 **Official Fix**: **YES**. <br>✅ **Solution**: Upgrade **Directorist Booking** to version **3.0.2** or later. <br>🔗 **Reference**: Patchstack database entry confirms the fix availability.

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: SQL Injection (SQLi) in **Directorist Booking** plugin.
💥 **Consequences**: Attackers can manipulate SQL commands via improper handling of special characters.…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: **CWE-89** (Improper Neutralization of Special Elements used in an SQL Command).…

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Affected Product**: **Directorist Booking** (WordPress Plugin).
📉 **Versions**: All versions **prior to 3.0.2**.
🌐 **Context**: Affects WordPress sites using this specific booking plugin.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

🕵️ **Attacker Capabilities**:
1. **Read**: Extract sensitive data (user credentials, bookings, personal info).
2. **Write**: Modify or delete database records.
3.…

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

🔓 **Exploitation Threshold**: **LOW**.
📊 **CVSS**: AV:N (Network), AC:L (Low Complexity), PR:N (No Privileges Required), UI:N (No User Interaction).…

Question 6

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

Accepted Answer

🧪 **Public Exploit**: **No**.
📝 **Status**: The `pocs` field is empty in the provided data. While the vulnerability is confirmed, no specific Proof-of-Concept (PoC) code is publicly listed in this dataset.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**:
1. **Scan**: Use vulnerability scanners to detect **Directorist Booking** version.
2. **Verify**: Check if version < **3.0.2**.
3.…

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

🩹 **Official Fix**: **YES**.
✅ **Solution**: Upgrade **Directorist Booking** to version **3.0.2** or later.
🔗 **Reference**: Patchstack database entry confirms the fix availability.

Question 9

What if no patch? (Workaround)

Accepted Answer

🛑 **No Patch Workaround**:
1. **Disable**: Deactivate/Deactivate the **Directorist Booking** plugin immediately.
2. **WAF**: Deploy a Web Application Firewall to block SQL injection patterns.
3.…

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

⚠️ **Urgency**: **HIGH**.
🚀 **Priority**: **P1**.
💡 **Reason**: Critical severity (C:H), easy exploitation (AC:L, PR:N), and wide attack surface (Network).…

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

CVE-2026-22336 — 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