CVE-2025-28062 is a cross-site request forgery vulnerability in ERPNext 14.82.1 and 14.74.3 caused by missing CSRF protections. An attacker can cause unauthorized application actions, including user deletion, password resets, and privilege escalation.
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).
This repository demonstrates a Cross-Site Request Forgery (CSRF) vulnerability (CVE-2025-28062) in ERPNext versions 14.82.1 and 14.74.3. The exploit consists of a proof-of-concept HTML file (PoC.html) and a detailed README.md. The PoC.html file contains links and scripts that, when visited by an authenticated ERPNext administrator, trigger unauthorized actions on the ERPNext instance by abusing the admin's session. These actions include user enumeration, user deletion, privilege escalation (adding roles), and password resets (account takeover). The README.md provides technical details, exploitation scenarios, and mitigation recommendations. The exploit targets ERPNext's administrative API endpoints, which lack CSRF protection, and leverages the browser as the attack vector. The endpoints are all local (http://localhost:8080), but in a real attack, these would be the actual ERPNext server addresses. The repository is structured as a simple PoC with no framework dependencies, and the exploit is a classic browser-based CSRF attack requiring the victim to be authenticated and to visit a malicious page.
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.