CVE-2024-54292 — AI Deep Analysis Summary

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

🚨 **Essence**: Unauthenticated SQL Injection (SQLi) in WordPress plugin **Appsplate**. 💥 **Consequences**: Attackers can extract sensitive database info, compromising site integrity & user data.

Q: Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-89** (SQL Injection). ❌ **Flaw**: Insufficient escaping of user-supplied parameters & lack of prepared statements in SQL queries.

Q: Who is affected? (Versions/Components)

📦 **Affected**: WordPress Plugin **Appsplate**. 📅 **Versions**: **2.1.3** and earlier.

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

🕵️ **Attacker Actions**: Append malicious SQL queries. 📊 **Impact**: Extract sensitive data from the database (High Confidentiality impact).

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

⚡ **Threshold**: **LOW**. 🔓 **Auth**: **Unauthenticated** (No login required). 🌐 **Access**: Network-accessible (AV:N).

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

💣 **Exploit**: **YES**. 🔗 **PoC**: Public PoC available on GitHub (RandomRobbieBF/CVE-2024-54292). 🔥 **Status**: Wild exploitation risk is high.

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

🔍 **Self-Check**: Scan for **Appsplate** plugin version **≤ 2.1.3**. 🧪 **Test**: Use provided PoC to test for SQLi via unauthenticated endpoints.

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

🩹 **Fix**: Update Appsplate plugin to **> 2.1.3**. 📢 **Source**: Vendor patch recommended. Check Patchstack for official details.

Q: What if no patch? (Workaround)

🚧 **No Patch?**: Disable the plugin immediately. 🛑 **Mitigate**: Restrict access to WordPress admin/API endpoints. Monitor DB logs for anomalies.

Q: Is it urgent? (Priority Suggestion)

🔴 **Priority**: **CRITICAL**. ⏱️ **Urgency**: Fix immediately. Unauthenticated SQLi is high-risk & easily exploitable.

Updated May 08, 2026 CVSS 9.3 · Critical

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**: Unauthenticated SQL Injection (SQLi) in WordPress plugin **Appsplate**. <br>💥 **Consequences**: Attackers can extract sensitive database info, compromising site integrity & user data.

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-89** (SQL Injection). <br>❌ **Flaw**: Insufficient escaping of user-supplied parameters & lack of prepared statements in SQL queries.

Q3Who is affected? (Versions/Components)

📦 **Affected**: WordPress Plugin **Appsplate**. <br>📅 **Versions**: **2.1.3** and earlier.

Q4What can hackers do? (Privileges/Data)

🕵️ **Attacker Actions**: Append malicious SQL queries. <br>📊 **Impact**: Extract sensitive data from the database (High Confidentiality impact).

Q5Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: **LOW**. <br>🔓 **Auth**: **Unauthenticated** (No login required). <br>🌐 **Access**: Network-accessible (AV:N).

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

💣 **Exploit**: **YES**. <br>🔗 **PoC**: Public PoC available on GitHub (RandomRobbieBF/CVE-2024-54292). <br>🔥 **Status**: Wild exploitation risk is high.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: Scan for **Appsplate** plugin version **≤ 2.1.3**. <br>🧪 **Test**: Use provided PoC to test for SQLi via unauthenticated endpoints.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Fix**: Update Appsplate plugin to **> 2.1.3**. <br>📢 **Source**: Vendor patch recommended. Check Patchstack for official details.

Q9What if no patch? (Workaround)

🚧 **No Patch?**: Disable the plugin immediately. <br>🛑 **Mitigate**: Restrict access to WordPress admin/API endpoints. Monitor DB logs for anomalies.

Q10Is it urgent? (Priority Suggestion)

🔴 **Priority**: **CRITICAL**. <br>⏱️ **Urgency**: Fix immediately. Unauthenticated SQLi is high-risk & easily exploitable.

Continue exploring

Vulnerability detail Full AI analysis (login) appsplate CWE-89