CVE-2015-3618
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 · uneditedCross-site scripting (XSS) vulnerability in Nagios Business Process Intelligence (BPI) before 2.3.4 allows remote attackers to inject arbitrary web script or HTML via vectors involving index.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 confidenceNagios Business Process Intelligence (BPI) before version 2.3.4 contains a reflected cross-site scripting (XSS) vulnerability in the index.php component. Attackers can inject arbitrary JavaScript or HTML through unsanitized user input processed by index.php, potentially allowing session hijacking or malicious content delivery to other users.
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< 2.3.4CVSS 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.0/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 Nagios BPI installationLocate the Nagios BPI installation directory and identify the presence of index.php and other BPI files. Common paths include /nagios/bpi/ or within the Nagios web root.Affected if Nagios BPI is present on the system with index.php accessible via web server
-
Identify installed BPI versionOpen the BPI index.php file or check for a version file within the BPI installation directory. Look for a version number defined in the code, a VERSION file, or the software release notes.Affected if The identified version is less than 2.3.4 (e.g., 2.3.3, 2.3.0, 1.x versions)
-
Verify index.php handles user inputExamine the index.php source code to confirm it processes user-supplied parameters (GET/POST requests) without proper sanitization. Look for unsanitized use of variables like $_GET, $_POST, or $_REQUEST.Affected if index.php directly uses user input in output (echo, print, HTML rendering) without sanitization functions such as htmlspecialchars() or equivalent
-
Check web exposure of vulnerable endpointVerify the index.php is accessible via the web server. Attempt to access the URL (e.g., http://your-server/nagios/bpi/index.php) and confirm it responds.Affected if index.php is web-accessible and accepts user parameters without filtering
If Nagios BPI is installed and the version is below 2.3.4 with index.php accessible and processing unsanitized user input, the environment is affected by this XSS vulnerability.
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 data2.3.4
Update Nagios BPI to version 2.3.4 or later which contains the security fix. If immediate patching is not feasible, implement proper input validation and output encoding on the index.php endpoint to neutralize XSS vectors.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3618 — 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-2015-3618 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