In GLPI (a free asset and IT management software), versions prior to 10.0.21 and 11.0.3 contain an access control weakness that allows an unauthorized user to access documents attached to arbitrary items (e.g., tickets, assets). When the public FAQ feature is enabled, the same unauthorized document access can be performed by an anonymous (unauthenticated) user. The issue is fixed in GLPI 10.0.21 and 11.0.3.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a proof-of-concept (POC) exploit for CVE-2025-64516, a SQL injection vulnerability. The exploit is documented in two markdown files (README.md and poc.md), both of which provide a crafted HTTP POST request targeting the /front/inventory.php endpoint. The request uses XML data with a malicious 'deviceid' parameter designed to exploit a SQL injection vulnerability and extract the database name from the backend. There is no executable code or scripts; the repository serves as a manual POC for researchers or penetration testers to reproduce the vulnerability. No specific product or vendor is mentioned, but the exploit is clearly network-based and targets web applications exposing the specified endpoint.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.