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 MetInfo CMS. π₯ **Consequences**: Attackers execute illegal SQL commands, compromising data integrity and confidentiality.
Q2Root Cause? (CWE/Flaw)
π‘οΈ **Root Cause**: Lack of validation for external SQL inputs. π **CWE**: Not specified in data, but clearly an input validation failure.
Q3Who is affected? (Versions/Components)
π― **Affected**: MetInfo CMS version **7.0.0beta**. π¦ **Component**: `language_general.class.php`.
Q4What can hackers do? (Privileges/Data)
π **Impact**: Execute arbitrary SQL. π **Privileges**: Database access, potential data theft or manipulation.
Q5Is exploitation threshold high? (Auth/Config)
π **Threshold**: Medium. Requires access to the admin language export function (`admin/?n=language...`).
Q6Is there a public Exp? (PoC/Wild Exploitation)
π **Exploit**: Yes. Public PoC available via Nuclei templates on GitHub. π **Wild Exploit**: Likely given public template availability.
Q7How to self-check? (Features/Scanning)
π **Check**: Scan for MetInfo 7.0.0beta. π§ͺ **Test**: Target the `doExportPack` parameter in the language admin module.