Security readout for executives and security teams
Plain-English summary
MantisBT before 2.25.3 can export CSV files that preserve attacker-controlled formula content. If a user opens that exported file in Excel, the spreadsheet may trigger harmful behavior, including code execution or information exposure. The attacker can be unprivileged, so exposure depends on whether users export and open issue data in Excel.
Executive priority
Treat this as a targeted operational risk, not an emergency internet-wide event. Prioritize upgrade where MantisBT is used for sensitive workflows or where CSV exports are routinely opened in Excel by privileged staff.
Technical view
CVE-2021-43257 is CSV formula injection in MantisBT's CSV API, specifically CSV output generated by csv_export.php. The issue is lack of neutralization of formula elements before export. The public CVE states MantisBT before 2.25.3 is affected. No CVSS vector, CWE, or KEV exploitation evidence is provided in the source bundle.
Likely exposure
Organizations running MantisBT versions before 2.25.3 are the likely exposure group, especially where unprivileged users can create issue content and staff export CSV data for Excel review.
Exploitation context
The source bundle does not show active exploitation, and CISA KEV status is false. Practical impact requires a user to open a generated CSV file in Excel. The CVE still matters because the attacker does not need privileged MantisBT access.
Researcher notes
Evidence is limited but consistent: the CVE description, MantisBT issue, and fix commit identify CSV formula neutralization failure before 2.25.3. No public CVSS, CWE mapping, affected CPE data, or confirmed exploitation is included in the supplied bundle.
Mitigation direction
- Upgrade MantisBT to version 2.25.3 or later.
- Review the linked MantisBT issue and commit for vendor-specific remediation details.
- Restrict CSV export access until affected instances are upgraded.
- Warn users not to open untrusted MantisBT CSV exports in Excel before remediation.
Validation and detection
- Inventory all MantisBT deployments and record their exact versions.
- Flag any deployment running a version earlier than 2.25.3.
- Confirm the deployed code includes the vendor fix commit or a later release.
- Review csv_export.php usage where low-privileged users can influence exported fields.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2021-43257 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.mantisbt.org/bugs/view.php?id=29130CVE reference · x_refsource_MISC
- https://github.com/mantisbt/mantisbt/commit/7f4534c723e3162b8784aebda4836324041dbc3eCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.