Cyber Resilience

CVE-2017-7615

Auth Bypass in Mantisbt ≤ 2.3.0

Public PoCHigh EPSSAuth Bypass
Published
16 April 2017
Modified
13 May 2026
Patch / advisory
View advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.91 99.8th percentile
Risk Priority 87 floored blend · peak EPSS

Summary

CVE-2017-7615 is a high-severity Weak Password Recovery Mechanism for Forgotten Password (CWE-640) vulnerability in Mantisbt Mantisbt. Its CVSS base score is 8.8 (High).

Operationally, ranked in the top 0.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

A07:2025 Authentication Failures

EU & UK References

Vulnerability Data

MantisBT through 2.3.0 allows arbitrary password reset and unauthenticated admin access via an empty confirm_hash value to verify.php.

CWE(s)
CWE-640

Related Threats

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1078 Valid Accounts Stealthconfidence: HIGH
Empty confirm_hash allows unauthenticated takeover of admin accounts, directly enabling use of valid high-privilege accounts.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Accessconfidence: HIGH
The flaw is in a public-facing web application (verify.php) and permits remote account compromise without authentication.
attack.mitre.org →
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2023-22476Same product: Mantisbt Mantisbt
CVE-2024-34080Same product: Mantisbt Mantisbt
CVE-2026-30849Same product: Mantisbt Mantisbt
CVE-2025-47776Same product: Mantisbt Mantisbt
CVE-2023-44394Same product: Mantisbt Mantisbt
CVE-2026-33517Same product: Mantisbt Mantisbt
CVE-2024-34081Same product: Mantisbt Mantisbt
CVE-2025-55155Same product: Mantisbt Mantisbt
CVE-2024-45792Same product: Mantisbt Mantisbt
CVE-2026-33548Same product: Mantisbt Mantisbt

Affected Assets

mantisbt
mantisbt
≤ 2.3.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V7.4.3

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

IA-5 Authenticator Management
addresses: CWE-640

Establishing procedures for lost or compromised authenticators addresses weak password recovery mechanisms.

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.AA-01 mostly match
prevents

Credential lifecycle management directly includes password reset/recovery flows.

PR.AA-02 mostly match
prevents

Identity proofing is the core control that prevents weak or bypassed recovery mechanisms.

PR.AA-03 partial match
prevents

Authentication policy covers strength/MFA but does not address recovery path weaknesses.

PR.PS-06 partial match
prevents

Secure SDLC reduces implementation flaws but is not specific to password-recovery design.

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.

A.5.17 Authentication information partial match
degrades

Strong authentication-information lifecycle rules directly address weak password-recovery flows.

A.8.25 Secure development life cycle partial match
prevents

Secure-SDLC practices can embed strong recovery design, yet the control is broader than this single weakness.

A.8.26 Application security requirements partial match
prevents

Application-security requirements can mandate secure recovery flows, but the control covers many other requirements.

A.8.28 Secure coding partial match
prevents

Secure-coding standards can prevent weak recovery implementations, yet the control is wider in scope.

A.8.5 Secure authentication partial match
mitigates

Secure-authentication requirements include robust forgotten-password procedures.

A.5.18 Access rights none match
none

Proper access-rights provisioning can limit who can trigger recovery, but does not fix the recovery mechanism itself.

References