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

🔧 **Official Fix**: **YES**. Update the BookingPress plugin to **version 1.0.11 or higher**. 📝 **Ref**: WordPress Trac changeset 2684789.

Q: What if no patch? (Workaround)

🚧 **Workaround**: If patching is delayed, disable the BookingPress plugin temporarily or restrict access to the `bookingpress_front_get_category_services` AJAX endpoint via WAF rules.

Q: Is it urgent? (Priority Suggestion)

⚡ **Priority**: **CRITICAL**. Unauthenticated SQLi allows immediate data breach. 🚀 **Action**: Patch immediately. Do not wait.

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: SQL Injection (SQLi) in BookingPress plugin. 💥 **Consequences**: Attackers can manipulate database queries via AJAX requests, leading to data theft or site compromise.

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

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

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Product**: BookingPress – Appointments Booking Calendar Plugin. 📉 **Affected**: Versions **before 1.0.11**. ✅ **Fixed**: In version 1.0.11 and later.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

🕵️ **Capabilities**: Dump WordPress user credentials, access database metadata, and perform arbitrary blind SQL injection. 📂 **Impact**: Full database access and potential server takeover.

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

🔓 **Threshold**: **LOW**. The exploit is **Unauthenticated**. No login or special configuration is needed to trigger the vulnerability via AJAX POST requests.

Question 6

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

Accepted Answer

💣 **Public Exp**: **YES**. Multiple PoCs exist on GitHub (Python, Bash scripts). 🌍 **Wild Exploitation**: High risk due to ease of use and unauthenticated nature.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Check**: Scan for BookingPress plugin version < 1.0.11. 🧪 **Test**: Use provided PoC scripts (e.g., `cve-2022-0739.py`) against the target URL to verify SQLi presence.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

🔧 **Official Fix**: **YES**. Update the BookingPress plugin to **version 1.0.11 or higher**. 📝 **Ref**: WordPress Trac changeset 2684789.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **Workaround**: If patching is delayed, disable the BookingPress plugin temporarily or restrict access to the `bookingpress_front_get_category_services` AJAX endpoint via WAF rules.

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

⚡ **Priority**: **CRITICAL**. Unauthenticated SQLi allows immediate data breach. 🚀 **Action**: Patch immediately. Do not wait.

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

CVE-2022-0739 — 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