Skip to content
Fencer Vulns
medium —

CVE-2026-52883 json

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

published 2026-07-15 3 mo ago modified 2026-07-15 3 mo ago also GHSA-4vpf-w7qv-5h3q

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

Unvalidated note_type Parameter in mc_issue_update SOAP Endpoint Allows creation of TIME_TRACKING and REMINDER Notes. The SOAP path passes the user-supplied note_type integer directly to bugnote_add() without validating that the user is authorized to create that type of note. If the user's access level is higher than *$g_time_tracking_view_threshold*, they can also inject arbitrary hours into billing reports.

REST API also allows injection of TIME_TRACKING notes (but not REMINDER) through the same mc_issue_update() function.

### Impact An attacker with UPDATER access could: - Inject fake billable hours via TIME_TRACKING notes (note_type=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 - https://github.com/mantisbt/mantisbt/commit/de2f71fd88746e963386c214c3ae65a3c4c851b7

### Workarounds None

### Resources - https://mantisbt.org/bugs/view.php?id=37081 - https://mantisbt.org/bugs/view.php?id=37200

### Credits Thanks to the following security researchers for discovering and responsibly reporting the issue - Vishal Shukla - Psalms Christopher Matovu (@byteoverride)

Patch / fix

  • packagist mantisbt/mantisbt 2.28.4

Affected packages

ecosystem package affected fixed in
packagist mantisbt/mantisbt
<2.28.4
2.28.4

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.