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**: A **Path Traversal** flaw in the GLPI Barcode plugin. ๐ **Consequences**: Attackers can read arbitrary files on the server, leading to **High** Confidentiality and Integrity impact.โฆ
๐ฏ **Affected**: **GLPI** instances running version **2.x**. ๐ฆ Specifically, those with the **Barcode plugin** installed. โ ๏ธ Versions **prior to 2.6.1** are vulnerable. If you have the plugin, you are at risk.
Q4What can hackers do? (Privileges/Data)
๐ต๏ธ **Attacker Capabilities**: Read **sensitive files** from the server filesystem. ๐ This includes configuration files, source code, or other data.โฆ
๐ **Exploitation Threshold**: **Low**. ๐ **Network** accessible (AV:N). โก **Low** complexity (AC:L). ๐ซ **No** authentication required (PR:N) and **No** user interaction needed (UI:N). It is an easy, remote attack vector.
Q6Is there a public Exp? (PoC/Wild Exploitation)
๐ฃ **Public Exploits**: **Yes**. ๐ PoCs are available on GitHub (e.g., AK-blank, ProjectDiscovery Nuclei templates). ๐ Wild exploitation is likely possible given the low barrier to entry and public tools.
Q7How to self-check? (Features/Scanning)
๐ **Self-Check**: Scan for GLPI instances with the **Barcode plugin**. ๐งช Use Nuclei templates or custom scripts targeting `front/send.php`. ๐ Check if the plugin version is **< 2.6.1**.โฆ
โ **Official Fix**: **Yes**. ๐ ๏ธ Patched in **Barcode plugin version 2.6.1**. ๐ Commit: `428c3d9adfb446e8492b1c2b7affb3d34072ff46`. Update immediately to the latest version.
Q9What if no patch? (Workaround)
๐ง **No Patch Workaround**: Delete the file `front/send.php` from the plugin directory. ๐๏ธ This removes the vulnerable entry point. โ ๏ธ Note: This may break barcode printing functionality, but it stops the leak.
Q10Is it urgent? (Priority Suggestion)
๐ฅ **Urgency**: **HIGH**. ๐จ CVSS Score indicates **Critical** impact on Confidentiality/Integrity. ๐โโ๏ธ Low exploitation barrier + Public PoCs = Immediate action required. Patch or apply workaround NOW.