MantisBT: Injection of TIME_TRACKING and REMINDER Notes via REST and SOAP APIs

Exploitation

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

CVSS 4.0

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Unvalidated notetype Parameter in mcissueupdate SOAP Endpoint Allows creation of TIMETRACKING and REMINDER Notes. The SOAP path passes the user-supplied notetype integer directly to bugnoteadd() without validating that the user is authorized to create that type of note. If the user's access level is higher than $gtimetrackingviewthreshold, they can also inject arbitrary hours into billing reports. REST API also allows injection of TIMETRACKING notes (but not REMINDER) through the same mcissueupdate() function. Impact An attacker with UPDATER access could: - Inject fake billable hours via TIMETRACKING notes (notetype=2), corrupting billing data exported through MantisBT's billing reports. Organizations that bill clients based on MantisBT time tracking data would generate incorrect invoices, and corrupt time tracking reports could be used to drive project management decisions. - Fake REMINDER notes registered (but without actual sending of notifications). Patches -…

Published by the source

15 Jul 2026, 18:52 UTC

Last modified by the source

15 Jul 2026, 18:52 UTC

Source last checked

26 Oct 2026, 14:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4vpf-w7qv-5h3q

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

# Patch Next advisory brief: CVE-2026-52883

Advisory: MantisBT: Injection of TIME_TRACKING and REMINDER Notes via REST and SOAP APIs
IDs: CVE-2026-52883, GHSA-4vpf-w7qv-5h3q
Record: https://patchnext.com/advisories/cve-2026-52883 (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: Medium (CVSS 5.3)
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-4vpf-w7qv-5h3q (GitHub-reviewed advisory GHSA-4vpf-w7qv-5h3q lists affected ranges: Packagist mantisbt/mantisbt >=0 <=2.28.3)

Commands are suggestions: review each one before running it.