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 'Contest Gallery' plugin. 📉 **Consequences**: Attackers can steal user lists (usernames & emails) and execute arbitrary SQL commands.…
🛡️ **CWE-89**: Improper Neutralization of Special Elements used in an SQL Command. 🐛 **Flaw**: The plugin fails to sanitize/escape the `cg-search-user-name-original` parameter before using it in SQL queries.…
🔓 **Threshold**: LOW. 🚫 **Auth**: No authentication needed (Unauthenticated). ⚙️ **Config**: Exploits the 'export users from gallery' feature. 🎯 **Ease**: Direct parameter manipulation via `cg-search-user-name-original`.
Q6Is there a public Exp? (PoC/Wild Exploitation)
📜 **PoC**: Yes, available via Nuclei templates (ProjectDiscovery). 🔍 **Detection**: Public YAML templates exist for automated scanning. 🌍 **Wild Exploit**: Likely widespread due to low barrier to entry and public PoCs.
Q7How to self-check? (Features/Scanning)
🔍 **Check**: Scan for 'Contest Gallery' plugin version < 13.1.0.6. 🧪 **Test**: Use Nuclei template `CVE-2021-24915.yaml`. 📡 **Indicator**: Look for SQL errors or unexpected data in user export endpoints.
Q8Is it fixed officially? (Patch/Mitigation)
✅ **Fixed**: Yes. 🔄 **Patch**: Upgrade Contest Gallery plugin to version **13.1.0.6** or later. 🛠️ **Vendor Action**: WordPress Foundation/Plugin developer released the fix.
Q9What if no patch? (Workaround)
🚧 **Workaround**: Disable the 'Contest Gallery' plugin immediately if patching isn't possible. 🚫 **Block**: Restrict access to the plugin's export endpoints via WAF or firewall rules.…