CVE-2024-36042 is an authentication bypass vulnerability in Silverpeas before version 6.3.5. The issue is triggered by sending a request to AuthenticationServlet with the Password field omitted. Under this condition, the application can improperly authenticate the requester, allowing an unauthenticated user to bypass normal login checks. The available information indicates that successful exploitation can result in access as a superadmin, implying a flaw in authentication logic or input handling within the authentication workflow.
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 (1 hidden).
Repository contains a single Python exploit script and a README. The main file, CVE-2024-36042.py, is a standalone Python 3 proof-of-concept for CVE-2024-36042 affecting Silverpeas versions earlier than 6.3.5. The exploit targets weak authentication handling in /silverpeas/AuthenticationServlet by submitting a login request without a Password parameter. It supports single-user targeting or multi-user attempts using a built-in username list or an external wordlist, and uses concurrent threads for faster enumeration. The script builds a requests session with browser-like headers, optional HTTP/HTTPS proxy support, and disabled TLS verification. It includes version fingerprinting by requesting /silverpeas/defaultLogin.jsp and parsing version-like strings from returned HTML/JS references. Successful exploitation is determined heuristically using cookies, redirects, URL changes, and authenticated-page content markers rather than a strict server-side success indicator. After bypass, the exploit can access /silverpeas/Main to confirm authenticated state and optionally scrape messages from /silverpeas/RSILVERMAIL/jsp/ReadMessage.jsp and /silverpeas/Rmessaging/jsp/ReadMessage.jsp. The README indicates support for multilingual discovery, message ID probing, deduplication, raw HTML capture, and export of harvested data to JSON, CSV, markdown, or individual text/markdown files. Output artifacts include summary.json, per-user message reports, raw HTML captures, and saved session cookies. Overall, this is a real exploit rather than a detector-only script. It is best classified as OPERATIONAL: it provides a working exploitation workflow and post-authentication data extraction, but it is still a standalone PoC rather than a reusable weaponized framework module.
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.