MantisBT: Stored XSS in print_all_bug_page_word.php

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.6 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

A missing output encoding call in printallbugpageword.php allows any authenticated user to inject arbitrary HTML into an IMG tag's alt attribute via an image attachment with a crafted filename such as probe." onload="alert(1). When any user views the HTML export page (printallbugpageword.php?typepage=html&export=1), the rendered IMG tag becomes <img src="..." alt="" onload="alert(1)" /, breaking out of the alt attribute. Impact Cross-site scripting. Impact is limited by MantisBT's Content Security Policy. Patches - https://github.com/mantisbt/mantisbt/commit/bdd0e364f62759de272dfd4c89b4f51d27be9daa Workarounds None Resources - https://mantisbt.org/bugs/view.php?id=37234 Credits MantisBT thanks the Dracosec Research Limited team (Chris Chan, Krecendo Hui, William Lam) for discovering and responsibly reporting the issue.

Published by the source

15 Jul 2026, 18:56 UTC

Last modified by the source

15 Jul 2026, 18:56 UTC

Source last checked

26 Oct 2026, 14:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h2wf-967x-gxvw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-62944

Advisory: MantisBT: Stored XSS in print_all_bug_page_word.php
IDs: CVE-2026-62944, GHSA-h2wf-967x-gxvw
Record: https://patchnext.com/advisories/cve-2026-62944 (revision 1, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mantisbt/mantisbt 2.28.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist mantisbt/mantisbt: affected <= 2.28.3; fixed in 2.28.4

## Suggested inspection (read-only)
- Packagist mantisbt/mantisbt: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mantisbt/mantisbt.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h2wf-967x-gxvw (GitHub-reviewed advisory GHSA-h2wf-967x-gxvw lists affected ranges: Packagist mantisbt/mantisbt >=0 <=2.28.3)

Commands are suggestions: review each one before running it.