Skip to content

Mantis Bug Tracker (MantisBT) vulnerable to cross-site scripting

Moderate severity GitHub Reviewed Published May 12, 2024 in mantisbt/mantisbt • Updated May 24, 2024

Package

composer mantisbt/mantisbt (Composer)

Affected versions

< 2.26.2

Patched versions

2.26.2

Description

Improper escaping of a custom field's name allows an attacker to inject HTML and, if CSP settings permit, achieve execution of arbitrary JavaScript when:

  • resolving or closing issues (bug_change_status_page.php) belonging to a project linking said custom field
  • viewing issues (view_all_bug_page.php) when the custom field is displayed as a column
  • printing issues (print_all_bug_page.php) when the custom field is displayed as a column

Impact

Cross-site scripting (XSS).

Patches

mantisbt/mantisbt@447a521

Workarounds

Ensure Custom Field Names do not contain HTML tags.

References

References

@dregad dregad published to mantisbt/mantisbt May 12, 2024
Published to the GitHub Advisory Database May 13, 2024
Reviewed May 13, 2024
Published by the National Vulnerability Database May 14, 2024
Last updated May 24, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L

EPSS score

0.045%
(17th percentile)

Weaknesses

CVE ID

CVE-2024-34081

GHSA ID

GHSA-wgx7-jp56-65mq

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.