CVE-2025-25150 — AI Deep Analysis Summary

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

🚨 **Essence**: Blind SQL Injection in uListing plugin. 📉 **Consequences**: Attackers can extract database data via time-based or error-based inference, potentially leading to full site compromise.

Q: Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-89** (SQL Injection). The flaw stems from improper neutralization of special elements in SQL queries, allowing malicious input to alter query logic.

Q: Who is affected? (Versions/Components)

🏢 **Affected**: **Stylemix** (Vendor). 📦 **Product**: **uListing** (WordPress Plugin). 📅 **Version**: **2.1.6 and earlier**. ⚠️ Any version ≤ 2.1.6 is at risk.

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

💀 **Hackers Can**: Extract sensitive data (users, configs). 🕵️ **Privileges**: Since it's Blind SQLi, they can infer data bit-by-bit. 🌐 **Impact**: High Confidentiality impact (C:H), Low Availability (A:L).

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

🔓 **Threshold**: **LOW**. 📝 **Auth**: None required (PR:N). 🖱️ **UI**: None required (UI:N). 🌍 **Network**: Remote (AV:N). 📉 **Complexity**: Low (AC:L). Easy to exploit remotely.

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

🚫 **Public Exp?**: **No**. The `pocs` array is empty in the provided data. 🔍 **Status**: Theoretical risk based on CVSS score, but no verified PoC or wild exploitation reported yet.

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

🔍 **Self-Check**: Scan for **uListing v2.1.6 or older**. 🛠️ **Tools**: Use SQLi scanners (e.g., SQLmap) on endpoints accepting unsanitized input. 📋 **Verify**: Check WordPress plugin directory for version number.

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

🩹 **Official Fix**: **Yes**. Update to a version **newer than 2.1.6**. 🔄 **Action**: Patch immediately via WordPress admin panel or manual upload. 📢 **Source**: Vendor (Stylemix) release notes.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. 📊 **CVSS**: 3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L. 🚀 **Priority**: Critical due to remote, unauthenticated, low-complexity exploitation. Patch ASAP.

Updated May 06, 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**: Blind SQL Injection in uListing plugin. 📉 **Consequences**: Attackers can extract database data via time-based or error-based inference, potentially leading to full site compromise.

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-89** (SQL Injection). The flaw stems from improper neutralization of special elements in SQL queries, allowing malicious input to alter query logic.

Q3Who is affected? (Versions/Components)

🏢 **Affected**: **Stylemix** (Vendor). 📦 **Product**: **uListing** (WordPress Plugin). 📅 **Version**: **2.1.6 and earlier**. ⚠️ Any version ≤ 2.1.6 is at risk.

Q4What can hackers do? (Privileges/Data)

💀 **Hackers Can**: Extract sensitive data (users, configs). 🕵️ **Privileges**: Since it's Blind SQLi, they can infer data bit-by-bit. 🌐 **Impact**: High Confidentiality impact (C:H), Low Availability (A:L).

Q5Is exploitation threshold high? (Auth/Config)

🔓 **Threshold**: **LOW**. 📝 **Auth**: None required (PR:N). 🖱️ **UI**: None required (UI:N). 🌍 **Network**: Remote (AV:N). 📉 **Complexity**: Low (AC:L). Easy to exploit remotely.

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

🚫 **Public Exp?**: **No**. The `pocs` array is empty in the provided data. 🔍 **Status**: Theoretical risk based on CVSS score, but no verified PoC or wild exploitation reported yet.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: Scan for **uListing v2.1.6 or older**. 🛠️ **Tools**: Use SQLi scanners (e.g., SQLmap) on endpoints accepting unsanitized input. 📋 **Verify**: Check WordPress plugin directory for version number.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Official Fix**: **Yes**. Update to a version **newer than 2.1.6**. 🔄 **Action**: Patch immediately via WordPress admin panel or manual upload. 📢 **Source**: Vendor (Stylemix) release notes.

Q9What if no patch? (Workaround)

🚧 **No Patch?**: 1. **Disable** the plugin if not essential. 2. **WAF**: Deploy Web Application Firewall rules to block SQL injection patterns. 3.…

Read full answer (login)

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. 📊 **CVSS**: 3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L. 🚀 **Priority**: Critical due to remote, unauthenticated, low-complexity exploitation. Patch ASAP.

Continue exploring

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