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 in WordPress plugin 'Simple Link Directory'. π₯ **Consequences**: Attackers can steal sensitive data, modify database records, or execute unauthorized admin actions.β¦
π‘οΈ **CWE**: CWE-89 (SQL Injection). π **Flaw**: The `qcopd_upvote_action` AJAX function accepts `post_id` without validation or escaping before using it in a SQL statement. Dirty data enters the database engine directly.
Q3Who is affected? (Versions/Components)
π¦ **Product**: WordPress Plugin: Simple Link Directory. π **Affected Versions**: All versions **before 7.7.2**. If you are running 7.7.1 or lower, you are vulnerable.
Q4What can hackers do? (Privileges/Data)
π΅οΈ **Attacker Capabilities**: 1. Extract sensitive info (user creds, DB structure). 2. Modify/Delete data. 3. Execute admin operations. π **Privilege**: Can be done by **unauthenticated** users (no login needed!).
Q5Is exploitation threshold high? (Auth/Config)
β‘ **Threshold**: **LOW**. π **Auth**: No authentication required. Any anonymous visitor on the internet can trigger the exploit via the AJAX endpoint. Config complexity is minimal.
Q6Is there a public Exp? (PoC/Wild Exploitation)
π₯ **Exploit Status**: **YES**. π **PoC**: Public Proof-of-Concept available via Nuclei templates (projectdiscovery). Wild exploitation is highly likely given the low barrier to entry.
Q7How to self-check? (Features/Scanning)
π **Self-Check**: 1. Scan for 'Simple Link Directory' plugin. 2. Check version number (must be < 7.7.2). 3. Use scanners like Nuclei with the specific CVE-2022-0760 template to test the `qcopd_upvote_action` endpoint.
Q8Is it fixed officially? (Patch/Mitigation)
β **Fix**: **YES**. π οΈ **Patch**: Update the plugin to version **7.7.2** or higher. The vendor confirmed the fix via WordPress Trac changeset 2684915.
Q9What if no patch? (Workaround)
π§ **No Patch Workaround**: 1. **Disable** the plugin immediately if update isn't possible. 2. **Block** access to the `qcopd_upvote_action` AJAX endpoint via WAF or firewall rules. 3.β¦
π¨ **Urgency**: **HIGH**. β³ **Priority**: Patch immediately. Since it requires **no authentication**, automated bots are likely already scanning for this. Delay increases risk of data breach significantly.