A cross-site scripting (XSS) vulnerability exists in Gitea versions 1.12.x and 1.13.x prior to 1.13.4, where certain issue data is not properly sanitized, allowing attackers to inject arbitrary JavaScript code in some situations.
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 full exploit chain for CVE-2021-28378, a client-side XSS vulnerability in Gitea (versions 1.12.0 to <1.13.4) that allows attackers to escalate privileges and achieve remote code execution. The repository contains: - A detailed README.md explaining the vulnerability, affected versions, and exploitation context. - exploit.py: A Python script that automates the attack. It logs into a target Gitea instance, creates a malicious repository and issue containing a JavaScript payload, and then posts a link to this issue in a victim's repository. Once the victim interacts with the crafted issue, the payload executes in their browser, escalating the attacker's privileges to admin. The script then sets up a malicious git hook to trigger a reverse shell to the attacker's machine. - exploit1.js, exploit2.js, exploit3.js: JavaScript payloads for use in XSS attacks. These scripts perform actions such as creating issues with stolen data, deleting repositories, and directly escalating a user to admin by sending crafted POST requests to the Gitea admin API. The exploit chain leverages both browser-based (XSS) and network-based vectors, targeting the Gitea web application and its API endpoints. The main endpoints involved are the Gitea web interface (http://mygitea.com or http://localhost:3000), the API for repository and user management, and the attacker's own IP for the reverse shell. The exploit is operational, providing a working privilege escalation and remote code execution path, and is not just a proof of concept.
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.
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.