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 (SQLi) in OSM β OpenStreetMap plugin. <br>π₯ **Consequences**: Attackers can extract sensitive data from the database.β¦
π‘οΈ **Root Cause**: CWE-89 (SQL Injection). <br>π **Flaw**: Insufficient escaping of user-supplied parameters. The plugin fails to properly sanitize inputs before querying the database.
π» **Attacker Actions**: Extract sensitive information from the database. <br>π **Privileges**: Requires **Authenticated** access. <br>π **Impact**: High (C:H, I:H, A:H) according to CVSS 3.1.
Q5Is exploitation threshold high? (Auth/Config)
β οΈ **Threshold**: Medium. <br>π **Requirement**: **Privileges Required: Low (PR:L)**. <br>π€ **Condition**: The attacker must be **authenticated** to exploit this vulnerability. It is not remote unauthenticated.
Q6Is there a public Exp? (PoC/Wild Exploitation)
π« **Public Exp?**: **No**. <br>π **PoC**: The `pocs` field is empty. No public Proof of Concept or wild exploitation code is currently available in the provided data.
Q7How to self-check? (Features/Scanning)
π **Self-Check**: <br>1. Check WordPress plugin list for **OSM β OpenStreetMap**. <br>2. Verify version is **β€ 6.0.2**. <br>3. Use scanners to detect SQLi patterns in plugin endpoints if authenticated.
Q8Is it fixed officially? (Patch/Mitigation)
β **Fixed?**: **Yes**. <br>π **Patch**: Reference to `plugins.trac.wordpress.org/changeset/3153019` indicates a fix was committed.β¦
π‘οΈ **Workaround**: <br>1. **Disable** the plugin if not strictly needed. <br>2. **Restrict access** to WordPress admin areas (since auth is required). <br>3.β¦