Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-rmp5-5jj7-gmvf

MantisBT has an authorization bypass that allows reading attachments after losing access to a private issue

CVSS 5.3 MediumEPSS 0.0036 · 30th percentile

Published by the GitHub Advisory Database at 11 May 2026, 19:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
mantisbt/mantisbtPackagist<2.28.22.28.2
Identifiers
GHSA-rmp5-5jj7-gmvf · CVE-2026-34744 · PKSA-mqx4-yq62-zbx3
Weakness (CWE)
CWE-200 · CWE-281
Tags
Published
11 May 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

MantisBT, as the Packagist package mantisbt/mantisbt before 2.28.2, lets a user keep listing and downloading attachments they uploaded to an issue created by someone else, even after that issue becomes private and the user no longer has direct access. An attacker needs only a prior account that was able to upload to the issue, and the source says the confidentiality impact is minimal because only the user's own previously uploaded attachments remain reachable. Upgrade to version 2.28.2, which contains the fix; the source lists no workarounds.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0036, the 30th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:01 UTC First seen by agentprime
  2. 31 Oct 2026, 14:01 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.