LiveActive security incident?Get immediate response
CVE Record

CVE-2009-20001: An issue was discovered in MantisBT before 2.24.5.

An issue was discovered in MantisBT before 2.24.5. It associates a unique cookie string with each user. This string is not reset upon logout (i.e., the user session is still considered valid and active), allowing an attacker who somehow gained access to a user's cookie to login as them.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

MantisBT versions before 2.24.5 did not properly end a user's cookie-based session at logout. If someone already obtained that cookie, logout would not stop them from using it to access the account.

Executive priority

Prioritize remediation for internet-facing or sensitive MantisBT instances. The issue enables account takeover only after cookie exposure, but logout not ending access weakens incident containment.

Technical view

The CVE describes persistent per-user cookie strings that were not reset on logout. The session could remain valid after logout, enabling account impersonation if an attacker had prior access to the user's cookie.

Likely exposure

Exposure is limited to organizations running MantisBT before 2.24.5. Publicly reachable instances and shared-device usage raise concern. The source bundle does not provide CPEs, CVSS, or detailed configuration scope.

Exploitation context

The bundle marks KEV as false and provides no evidence of active exploitation. The described attack depends on prior cookie access, but the sources do not describe how that access is obtained.

Researcher notes

The public data is sparse: no CVSS, CWE, CPE, or exploitation evidence is included. Analysis should remain scoped to MantisBT before 2.24.5 and the logout cookie invalidation failure.

Mitigation direction

  • Upgrade MantisBT to 2.24.5 or later where applicable.
  • Review the linked MantisBT issues for vendor-specific guidance.
  • Invalidate active sessions after upgrade if the product supports it.
  • Treat exposed session cookies as compromised during incident response.

Validation and detection

  • Inventory MantisBT deployments and confirm their exact versions.
  • Check whether any instance is running a version before 2.24.5.
  • Review authentication logs for suspicious reuse after user logout.
  • Confirm session invalidation behavior in a controlled test environment.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2009-20001 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.