Security readout for executives and security teams
Plain-English summary
MantisBT versions before 2.24.2 have a stored cross-site scripting flaw in issue listing behavior. If an attacker can save crafted HTML in a text Custom Field, other users viewing the issue may run attacker-controlled browser code, depending on CSP settings.
Executive priority
Treat this as a near-term remediation item for any internet-facing or broadly used MantisBT instance, especially where many users can edit issues. It is not supported as actively exploited by the provided sources.
Technical view
The issue is improper escaping in view_all_bug_page.php. Content saved into a text Custom Field can be rendered as HTML on later issue views, creating stored XSS. The CVE bundle provides no CVSS, CWE, or detailed affected CPE metadata.
Likely exposure
Exposure is likely limited to MantisBT deployments before 2.24.2 where users or attackers can write text Custom Fields and other users view affected issues.
Exploitation context
The provided bundle does not report active exploitation, and KEV is false. Exploitation requires saving malicious field content and having another user view the issue; impact depends partly on CSP settings.
Researcher notes
Evidence is sufficient for product and version direction but incomplete for severity scoring. The main validation target is stored XSS through text Custom Fields rendered by view_all_bug_page.php in MantisBT before 2.24.2.
Mitigation direction
- Upgrade MantisBT to version 2.24.2 or later.
- Review the MantisBT issue and release advisory for vendor guidance.
- Ensure CSP is configured to reduce script execution risk.
- Restrict who can edit text Custom Fields until upgraded.
Validation and detection
- Inventory MantisBT deployments and confirm their exact versions.
- Check whether text Custom Fields are enabled and user-writable.
- Review CSP configuration for MantisBT pages.
- Audit recent Custom Field values for unexpected HTML content.
- Confirm view_all_bug_page.php behavior is fixed after upgrade.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-16266 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://mantisbt.org/bugs/view.php?id=27056CVE reference · x_refsource_CONFIRM
- https://mantisbt.org/blog/archives/mantisbt/665CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.