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 via User-Controlled SQL Primary Key. <br>π₯ **Consequences**: Full system compromise. Attackers can bypass authorization controls, leading to data theft, modification, or destruction.β¦
π‘οΈ **Root Cause**: **CWE-566** (Authorization Bypass Through SQL Logic). <br>π **Flaw**: The software fails to properly validate or sanitize user inputs when used as SQL primary keys.β¦
π **Self-Check Methods**: <br>1. **Version Check**: Verify if your installed version is β€ 19022026. <br>2. **Input Testing**: Try injecting SQL syntax (e.g., `' OR 1=1 --`) into fields that map to SQL primary keys.β¦
π οΈ **Official Fix**: **Unknown/Not Provided**. <br>π **Published**: 2026-02-19. <br>π **Reference**: USOM Advisory (tr-26-0078). <br>β οΈ **Action**: Check the vendor's official website or the USOM link for a patch.β¦
π₯ **Urgency**: **CRITICAL**. <br>π **Priority**: **P1 (Immediate Action)**. <br>π‘ **Reason**: CVSS Score is **9.1** (High). It is remote, requires no authentication, and has severe impact.β¦