CVE-2022-3982 — AI Deep Analysis Summary

Q: What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Arbitrary File Upload in Booking Calendar plugin. 💥 **Consequences**: Leads to Remote Code Execution (RCE). Attackers can run malicious code on the server.

Q: Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: Lack of file validation. 🔍 **Flaw**: The plugin does not verify uploaded files, allowing malicious payloads (like PHP) to bypass security checks.

Q: Who is affected? (Versions/Components)

📦 **Affected**: WordPress Plugin **Booking Calendar**. 📅 **Version**: Versions **before 3.2.2** are vulnerable.

Q: What can hackers do? (Privileges/Data)

💀 **Attacker Capabilities**: 1. Upload arbitrary files (PHP shells). 2. Execute unauthorized operations. 3. Modify data or steal sensitive info via RCE.

Q: Is exploitation threshold high? (Auth/Config)

🔓 **Threshold**: **LOW**. 👤 **Auth**: **Unauthenticated**. No login required to exploit the file upload flaw.

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

🔥 **Exploit Status**: **YES**. 📂 **PoC**: Public Nuclei template available on GitHub (projectdiscovery). Wild exploitation is possible.

Q: How to self-check? (Features/Scanning)

🔍 **Self-Check**: 1. Scan for **Booking Calendar** plugin. 2. Check version number (< 3.2.2). 3. Use Nuclei template `CVE-2022-3982.yaml` for automated detection.

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

🩹 **Fix**: Upgrade plugin to **version 3.2.2 or later**. ✅ **Official Patch**: The vulnerability is fixed in the updated release.

Q: What if no patch? (Workaround)

🚧 **No Patch Workaround**: 1. **Disable/Deactivate** the Booking Calendar plugin immediately. 2. Restrict file upload permissions via server config (WAF).

Q: Is it urgent? (Priority Suggestion)

⚡ **Priority**: **CRITICAL**. 🚨 **Reason**: Unauthenticated RCE + Public PoC = High risk of immediate compromise. Patch NOW!

Updated May 08, 2026

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**: Arbitrary File Upload in Booking Calendar plugin. <br>💥 **Consequences**: Leads to Remote Code Execution (RCE). Attackers can run malicious code on the server.

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: Lack of file validation. <br>🔍 **Flaw**: The plugin does not verify uploaded files, allowing malicious payloads (like PHP) to bypass security checks.

Q3Who is affected? (Versions/Components)

📦 **Affected**: WordPress Plugin **Booking Calendar**. <br>📅 **Version**: Versions **before 3.2.2** are vulnerable.

Q4What can hackers do? (Privileges/Data)

💀 **Attacker Capabilities**: <br>1. Upload arbitrary files (PHP shells). <br>2. Execute unauthorized operations. <br>3. Modify data or steal sensitive info via RCE.

Q5Is exploitation threshold high? (Auth/Config)

🔓 **Threshold**: **LOW**. <br>👤 **Auth**: **Unauthenticated**. No login required to exploit the file upload flaw.

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

🔥 **Exploit Status**: **YES**. <br>📂 **PoC**: Public Nuclei template available on GitHub (projectdiscovery). Wild exploitation is possible.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: <br>1. Scan for **Booking Calendar** plugin. <br>2. Check version number (< 3.2.2). <br>3. Use Nuclei template `CVE-2022-3982.yaml` for automated detection.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Fix**: Upgrade plugin to **version 3.2.2 or later**. <br>✅ **Official Patch**: The vulnerability is fixed in the updated release.

Q9What if no patch? (Workaround)

🚧 **No Patch Workaround**: <br>1. **Disable/Deactivate** the Booking Calendar plugin immediately. <br>2. Restrict file upload permissions via server config (WAF).

Q10Is it urgent? (Priority Suggestion)

⚡ **Priority**: **CRITICAL**. <br>🚨 **Reason**: Unauthenticated RCE + Public PoC = High risk of immediate compromise. Patch NOW!

Continue exploring

Vulnerability detail Full AI analysis (login) Unknown