CVE-2009-2802
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMantisBT 1.2.x before 1.2.2 insecurely handles attachments and MIME types. Arbitrary inline attachment rendering could lead to cross-domain scripting or other browser attacks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMantisBT 1.2.x before 1.2.2 improperly processes attachments and their MIME types, allowing arbitrary inline rendering of uploaded files. This enables attackers to inject malicious content that executes in users' browsers, leading to cross-site scripting or other client-side attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.2.0, < 1.2.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine MantisBT versionCheck the version.php file in the MantisBT root directory, or log into the admin section to view system informationAffected if The installed version is 1.2.0 or 1.2.1 (versions >= 1.2.0 and < 1.2.2 are affected)
-
Verify attachment feature is enabledExamine config.php for $g_allow_file_upload setting, or check the bug attachments list in a project to see if files have been uploadedAffected if Attachments are enabled and users have uploaded files to bugs or projects
-
Inspect how the server serves attachment filesCheck the web server configuration (Apache/Nginx) and MantisBT config for how attachments are delivered; use browser developer tools to inspect the Content-Disposition header when downloading an attachmentAffected if Attachments are served with Content-Disposition: inline instead of Content-Disposition: attachment
-
Review MIME type handling for uploadsExamine config.php for $g_allowed_files and $g_file_upload_methods settings; verify if there is any MIME type allow-listing or validation in placeAffected if There is no strict MIME type allow-listing or the configuration allows arbitrary file types to be rendered inline
A user is affected if running MantisBT 1.2.0 or 1.2.1, the attachment feature is enabled, and attachments can be rendered inline without proper Content-Disposition headers or MIME type restrictions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.2.2
Upgrade to MantisBT 1.2.2 or later. Until then, configure the server to serve attachments with Content-Disposition: attachment headers and implement strict MIME type allow-listing for uploads.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-2802 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-2802 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data