CVE-2018-16362
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 · uneditedAn issue was discovered in the Source Integration plugin before 1.5.9 and 2.x before 2.1.5 for MantisBT. A cross-site scripting (XSS) vulnerability in the Manage Repository and Changesets List pages allows execution of arbitrary code (if CSP settings permit it) via repo_manage_page.php or list.php.
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 confidenceCross-site scripting (XSS) vulnerability in the Source Integration plugin for MantisBT allows authenticated attackers to inject malicious JavaScript via the Manage Repository page (repo_manage_page.php) or Changesets List page (list.php) by crafting malicious input in repository-related fields.
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.5.9>= 2.0.0, < 2.1.5CVSS 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.
-
Confirm MantisBT installationLook for MantisBT web application files (e.g., core.php, api/soap/mantisconnect.php) or check HTTP response headers for 'MantisBT' stringAffected if MantisBT is not present on the system
-
Identify Source Integration plugin presenceCheck for the Source Integration plugin directory (typically 'plugins/Source' or 'plugins/sourceintegration' under MantisBT root) or query the MantisBT database plugin table if database access is availableAffected if Source Integration plugin is not installed
-
Verify plugin is enabledCheck MantisBT configuration file config_inc.php for plugin enablement or inspect the plugin management interface via admin/plugin Manage Plugins pageAffected if Plugin is installed but disabled - vulnerability does not apply
-
Determine Source Integration plugin versionOpen the plugin's info file (e.g., Source/Info.php or Source/pages/info.php) and locate the 'version' declaration, or view the plugin details in MantisBT's plugin management pageAffected if Version is 1.5.9 or higher, or version 2.1.5 or higher - these are patched versions
-
Identify vulnerable plugin pagesCheck if repo_manage_page.php and list.php exist within the Source plugin directory (Source/pages/repo_manage_page.php and Source/pages/list.php)Affected if These pages exist and are accessible to authenticated users - XSS can be injected into repository-related fields on these pages
User is affected if MantisBT with Source Integration plugin is running with plugin version below 1.5.9 or between 2.0.0 and 2.1.4, and the plugin is enabled and accessible to authenticated users.
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.5.92.1.5
Upgrade the Source Integration plugin to version 1.5.9 or 2.1.5 or later to obtain the security patch, or temporarily disable the plugin until the upgrade can be completed.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16362 — 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-2018-16362 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