Loading vulnerability…
Kaiten 57.128.8 contains an observable login-response discrepancy that permits remote user-account enumeration. A crafted POST request can distinguish whether an account exists because the login response includes the user_email field only for existing user accounts.
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 provides a proof-of-concept exploit for CVE-2024-39211, a user enumeration vulnerability in the Kaiten workflow management system. The main exploit is a Bash script (CVE-2024-39211.sh) that takes a target host and a dictionary file of usernames as input. It iterates through the usernames, sending POST requests to the /login endpoint of the Kaiten instance over HTTPS. If the response contains a 'user_email' field, the script extracts and prints the email address, effectively confirming the existence of the username and revealing the associated email. The README provides usage instructions, references, and links to suitable wordlists for brute-forcing. The exploit is network-based, targeting the exposed login endpoint of Kaiten, and is intended for user enumeration rather than full system compromise. The repository is structured simply, with the Bash script as the main code file and a README for documentation.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.