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 Sentrifugo HRMS. ๐ **Consequences**: Attackers can extract **ALL** database data via the `/reports/businessunits/format/html` endpoint.โฆ
๐ก๏ธ **Root Cause**: **CWE-89** (SQL Injection). ๐ **Flaw**: The `bunitname` parameter in the `index.php` script fails to sanitize input, allowing malicious SQL queries to execute directly on the server.
Q3Who is affected? (Versions/Components)
๐ข **Affected**: **Sentrifugo** HR Management System. ๐ฆ **Version**: Specifically **v3.2**. ๐ **Component**: The `reports/businessunits` module is the entry point.
Q4What can hackers do? (Privileges/Data)
๐ **Capabilities**: Hackers can bypass logic and dump the entire database. ๐ **Data**: Access to sensitive HR, performance, and asset records.โฆ
โก **Threshold**: **LOW**. ๐ซ **Auth**: None required (PR:N). ๐ **Network**: Remote (AV:N). ๐ฏ **Complexity**: Low (AC:L). Easy to exploit for anyone with network access.
Q6Is there a public Exp? (PoC/Wild Exploitation)
๐ **Public Exp**: No specific PoC code provided in the data. ๐ **Status**: Reference link exists (Incibe), but no executable exploit script is listed in the `pocs` array.
Q7How to self-check? (Features/Scanning)
๐ **Check**: Scan for the path `/sentrifugo/index.php/reports/businessunits/format/html`. ๐งช **Test**: Inject SQL payloads into the `bunitname` parameter.โฆ
๐ ๏ธ **Fix**: Official patch info is not detailed in the provided text. ๐ **Action**: Check the vendor's official notice (Incibe link) for the latest patch or update instructions.
Q9What if no patch? (Workaround)
๐ง **Workaround**: If no patch, **disable** the `/reports/businessunits` endpoint. ๐ **Block**: Restrict access to `index.php` via WAF or firewall rules.โฆ