Loading vulnerability…
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.
This repository is a compact Bash-based proof-of-concept for CVE-2026-53625 affecting GLPI. It contains only two files: a README describing the vulnerability and usage, and a single executable script, poc_authtype_takeover.sh, which is the main exploit entry point. The script is not part of a larger exploit framework. The exploit targets GLPI's REST API authorization weakness around user updates. According to the repository, a low-privilege Technician can update another user's record and set authtype to EXTERNAL. GLPI then clears the victim's password, producing either immediate account lockout (DoS) or, when header-based SSO is deployed and the Remote-User header is forgeable, full account takeover. The takeover chain described by the code and README is: authenticate to the API, enumerate users, select a Super-Admin victim, modify the victim's authtype, impersonate the victim via forged Remote-User header, switch to the privileged profile, and create a persistent backdoor account. The script also supports optional restoration of the victim account by resetting authtype and assigning a new password. Repository structure is minimal and purpose-built. README.md documents affected versions, attack flow, prerequisites, and CLI examples. poc_authtype_takeover.sh implements argument parsing, attack mode selection (--lockdown for DoS, --backdoor for full takeover), safe mode, verbose output, auto-targeting, temporary workspace creation, cookie/session handling, API request wrappers, cleanup, and final reporting. The code clearly goes beyond detection: it performs active exploitation and persistence creation. Because the payload is embedded as fixed Bash logic rather than a reusable framework module, the maturity is best classified as OPERATIONAL rather than WEAPONIZED.
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.
2 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.