dbcve.org
MantisbtApplication

CVE-2022-26144

MEDIUM · 6.1 CVSS v3.1 Published 2022-04-13
Fix available
A fix is available. Upgrade to 2.25.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
An XSS issue was discovered in MantisBT before 2.25.3. Improper escaping of a Plugin name allows execution of arbitrary code (if CSP allows it) in manage_plugin_page.php and manage_plugin_uninstall.php when a crafted plugin is installed.

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 · high confidence

Cross-site scripting (XSS) vulnerability in MantisBT before version 2.25.3 allows attackers to inject malicious JavaScript code through improperly escaped plugin names displayed in manage_plugin_page.php and manage_plugin_uninstall.php. When a crafted plugin is installed, the plugin name is rendered without proper sanitization, enabling arbitrary script execution in victim browsers (mitigated by Content Security Policy).

MitigationUpgrade to MantisBT 2.25.3 or later which implements proper escaping of plugin names. Until patched, ensure Content Security Policy headers are properly configured to mitigate XSS 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
MantisbtApplication
Affected:< 2.25.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify MantisBT installation version
    Access the admin page or check the config file (config.php) for the version number, or view the footer of MantisBT pages which typically displays the version
    Affected if The installed version is any release before 2.25.3 (e.g., 2.25.0, 2.25.1, 2.25.2, or earlier)
  2. Confirm access to plugin management pages
    Navigate to manage_plugin_page.php and manage_plugin_uninstall.php through the MantisBT web interface (typically at /manage_plugin_page.php and /manage_plugin_uninstall.php under the MantisBT root URL)
    Affected if These pages are accessible without authentication bypass or the server responds to these endpoints
  3. Check for untrusted or unknown plugins
    Review the installed plugins list in the plugin management interface - look for any plugins with unusual names, recently added plugins, or plugins you did not intentionally install
    Affected if Any plugin is installed with a name containing special characters (such as <script>, javascript:, or other XSS vectors) that could execute in the browser

You are affected if your MantisBT version is below 2.25.3 AND you have any plugin installed, particularly one with a crafted name that could trigger XSS when viewing the plugin management pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2.25.3 or later
Fixed in 2.25.3
Interim mitigation

Upgrade to MantisBT 2.25.3 or later which implements proper escaping of plugin names. Until patched, ensure Content Security Policy headers are properly configured to mitigate XSS attacks.

Recommended fix High confidence

2.25.3

  1. 1. Backup your MantisBT database and files before proceeding with any upgrade
  2. 2. Download MantisBT version 2.25.3 or later from the official mantisbt.org repository
  3. 3. Extract the new version files to a temporary location
  4. 4. Copy the config/config_inc.php file from your existing installation to preserve your database credentials and settings
  5. 5. Replace the existing MantisBT installation files with the new version files, preserving your configuration
  6. 6. Verify the manage_plugin_page.php and manage_plugin_uninstall.php files have been updated to include proper escaping of plugin names
  7. 7. Clear any caches if your installation uses caching
  8. 8. Test that you can access the Manage Plugins page without errors

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mantisbt Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26144 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26144 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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