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**: SQL Injection (SQLi) in Pricing Table Plugin. <br>💥 **Consequences**: Attackers can steal sensitive data, modify database records, or execute unauthorized admin operations via AJAX requests.
Q2Root Cause? (CWE/Flaw)
🛡️ **Root Cause**: **CWE-89** (SQL Injection). <br>🔍 **Flaw**: Failure to properly sanitize and escape user-supplied **POST data** before inserting it into SQL statements.
Q3Who is affected? (Versions/Components)
📦 **Affected**: WordPress Plugin **Pricing Table** (also referred to as ARPrice). <br>📉 **Version**: Versions **prior to 3.6.1**.
Q4What can hackers do? (Privileges/Data)
🕵️ **Hackers Can**: Obtain sensitive information, modify existing data, and execute unauthorized administrative operations within the context of the affected WordPress site.
Q5Is exploitation threshold high? (Auth/Config)
⚡ **Threshold**: **Low**. Exploitation is triggered via **AJAX actions** using POST data. No complex authentication bypass is mentioned, making it relatively accessible.
Q6Is there a public Exp? (PoC/Wild Exploitation)
📜 **Public Exp?**: **Yes**. Proof of Concept (PoC) is available via **Nuclei templates** on GitHub (projectdiscovery/nuclei-templates).
Q7How to self-check? (Features/Scanning)
🔎 **Self-Check**: Scan for the **Pricing Table** plugin version < 3.6.1. Use automated scanners like **Nuclei** with the specific CVE-2022-0867 template to detect the SQLi vector.
Q8Is it fixed officially? (Patch/Mitigation)
🛠️ **Fix**: Upgrade the **Pricing Table** plugin to version **3.6.1** or later. This version addresses the sanitization and escaping issues.
Q9What if no patch? (Workaround)
🚧 **No Patch Workaround**: If upgrading isn't immediate, restrict **POST** access to the plugin's AJAX endpoints via WAF rules. However, patching is the only true fix for input validation flaws.
Q10Is it urgent? (Priority Suggestion)
🔥 **Urgency**: **High**. SQLi allows full database compromise. With public PoCs available, immediate patching is recommended to prevent data theft or site takeover.