Stored XSS via unescaped repository name
Published Feb 13, 2020 · Updated Aug 4, 2024
Stored XSS in MantisBT Source Integration before 1.6.2 and 2.0.0 through 2.3.0 allows remote attackers to run script in a user's browser. In Source/pages/repo_delete.php, helper_ensure_confirmed() inserts the stored repository name into the deletion-confirmation message without HTML encoding. The payload runs when a user opens the Delete Repository page, and execution depends on CSP settings permitting the injected script.
Summary
What happened
Stored XSS in MantisBT Source Integration before 1.6.2 and 2.0.0 through 2.3.0 allows remote attackers to run script in a user's browser. In Source/pages/repo_delete.php, helper_ensure_confirmed() inserts the stored repository name into the deletion-confirmation message without HTML encoding. The payload runs when a user opens the Delete Repository page, and execution depends on CSP settings permitting the injected script.
The record
- CVE
- CVE-2020-8981
- Published
- Feb 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 13, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Repository-name stored XSS reproduction stepsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo