GHSA-4VPF-W7QV-5H3Q

Vulnerability from github – Published: 2026-07-15 18:52 – Updated: 2026-07-15 18:52
VLAI
Summary
MantisBT: Injection of TIME_TRACKING and REMINDER Notes via REST and SOAP APIs
Details

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)

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 2.28.3"
      },
      "package": {
        "ecosystem": "Packagist",
        "name": "mantisbt/mantisbt"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.28.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-52883"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-20"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-07-15T18:52:20Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "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\u0027s access level is higher than *$g_time_tracking_view_threshold*, they can also inject arbitrary hours into billing reports.\n\nREST API also allows injection of TIME_TRACKING notes (but not REMINDER) through the same mc_issue_update() function.\n\n### Impact\nAn attacker with UPDATER access could:\n- Inject fake billable hours via TIME_TRACKING notes (note_type=2), corrupting billing data exported through MantisBT\u0027s 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.\n- Fake REMINDER notes registered (but without actual sending of notifications).\n\n### Patches\n- https://github.com/mantisbt/mantisbt/commit/de2f71fd88746e963386c214c3ae65a3c4c851b7\n\n### Workarounds\nNone\n\n### Resources\n- https://mantisbt.org/bugs/view.php?id=37081\n- https://mantisbt.org/bugs/view.php?id=37200\n\n### Credits\nThanks to the following security researchers for discovering and responsibly reporting the issue\n- Vishal Shukla\n- Psalms Christopher Matovu (@byteoverride)",
  "id": "GHSA-4vpf-w7qv-5h3q",
  "modified": "2026-07-15T18:52:20Z",
  "published": "2026-07-15T18:52:20Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/mantisbt/mantisbt/security/advisories/GHSA-4vpf-w7qv-5h3q"
    },
    {
      "type": "WEB",
      "url": "https://github.com/mantisbt/mantisbt/commit/de2f71fd88746e963386c214c3ae65a3c4c851b7"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/mantisbt/mantisbt"
    },
    {
      "type": "WEB",
      "url": "https://mantisbt.org/bugs/view.php?id=37081"
    },
    {
      "type": "WEB",
      "url": "https://mantisbt.org/bugs/view.php?id=37200"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "MantisBT: Injection of TIME_TRACKING and REMINDER Notes via REST and SOAP APIs"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…