Security Resilience

CVE-2025-55155

Info Disclosure in Mantisbt ≤ 2.27.2

Public PoCInfo Disclosure
Published
04 November 2025
Modified
19 October 2026
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0016 5th percentile
Risk Priority 41 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-55155 is a medium-severity Insertion of Sensitive Information Into Sent Data (CWE-201) vulnerability in Mantisbt. Its CVSS base score is 5.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Cloud Instance Metadata API (T1552.005); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Mantis Bug Tracker (MantisBT) is an open source issue tracker. In versions 2.27.1 and below, when a user edits their profile to change their e-mail address, the system saves it without validating that it actually belongs to the user. This…

more

could result in storing an invalid email address, preventing the user from receiving system notifications. Notifications sent to another person's email address could lead to information disclosure. This issue is fixed in version 2.27.2.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1552.005 Cloud Instance Metadata API Credential Access
Adversaries may attempt to access the Cloud Instance Metadata API to collect credentials and other sensitive data.
T1584.008 Network Devices Resource Development
Adversaries may compromise third-party network devices that can be used during targeting.
T1040 Network Sniffing Credential Access
Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.
T1565.002 Transmitted Data Manipulation Impact
Adversaries may alter data en route to storage or other systems in order to manipulate external outcomes or hide activity, thus threatening the integrity of the data.
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-34077Same product: Mantisbt Mantisbt
CVE-2025-46556Same product: Mantisbt Mantisbt
CVE-2026-33548Same product: Mantisbt Mantisbt
CVE-2024-34081Same product: Mantisbt Mantisbt
CVE-2026-33517Same product: Mantisbt Mantisbt
CVE-2017-7615Same product: Mantisbt Mantisbt
CVE-2025-47776Same product: Mantisbt Mantisbt
CVE-2026-30849Same product: Mantisbt Mantisbt
CVE-2025-62520Same product: Mantisbt Mantisbt
CVE-2023-44394Same product: Mantisbt Mantisbt

Affected Assets

mantisbt
mantisbt
≤ 2.27.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 11 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V14.2.3
  • V10.4.12

Mitigating Controls (NIST 800-53 r5) AI

Directly enforces policy-based information flow rules that block transmission of sensitive data to unauthorized actors.

Requires integrity verification tools that detect unauthorized changes when checksum validation is missing or flawed.

Enforces authorizations on logical access so that sensitive data is not released to unauthorized recipients.

Mandates cryptographic mechanisms that include integrity protection, preventing improper checksum validation.

Requires protection of transmitted information integrity, directly mandating correct validation of integrity checks.

Requires validation of outbound information to ensure sensitive content is not disclosed in responses or messages.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-01 mostly match
blocks

Requires cryptographic hashes and signatures that directly enforce integrity-check validation for data at rest.

PR.DS-02 mostly match
blocks

Requires cryptographic hashes and signatures that directly enforce integrity-check validation for data in transit.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly prevent insertion of sensitive data into application outputs and messages.

DE.CM-09 partial match
blocks

Monitoring runtime data flows and outputs can detect sensitive data being transmitted.

ID.RA-09 partial match
blocks

Mandates pre-acquisition integrity assessment, addressing only the initial portion of the weakness lifecycle.

PR.DS-10 partial match
blocks

Protecting data-in-use includes removing confidential values before they are processed or sent.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

Data-masking techniques can prevent sensitive values from appearing in transmitted payloads.

blocks

Cryptographic controls mandate integrity mechanisms whose correct validation directly prevents CWE-354.

finds

Security testing can detect missing integrity validation but does not itself implement the control.

prevents

Secure-coding standards explicitly forbid hard-coded or unfiltered sensitive data in outbound messages.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).

Oracle Linux 8 (2 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. blocks CWE-354
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-354
Oracle Linux 9 (1 rule)
  • V-271523 OL 9 must check the GPG signature of locally installed software packages before installation. blocks CWE-354
RHEL 7 (2 rules)
  • V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-354
  • V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-354
RHEL 8 (2 rules)
  • V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-354
  • V-230265 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-354

References