ZabbixApplication · Mesilat
CVE-2018-18289
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 · uneditedThe MESILAT Zabbix plugin before 1.1.15 for Atlassian Confluence allows attackers to read arbitrary files.
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 confidenceThe MESILAT Zabbix plugin before version 1.15.1 for Atlassian Confluence contains a path traversal vulnerability that allows authenticated or unauthenticated attackers to read arbitrary files on the server filesystem by manipulating file path parameters in the plugin's API endpoints.
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
ZabbixApplication
< 1.1.15CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Identify if MESILAT Zabbix plugin is installedIn Confluence administration, navigate to the 'Manage add-ons' or 'Apps' section and look for 'MESILAT Zabbix' or 'Zabbix' in the list of installed pluginsAffected if The plugin appears in the installed add-ons list
-
Determine the installed plugin versionClick on the MESILAT Zabbix plugin entry in the Manage add-ons page to view its details; the version number is displayed thereAffected if The version shown is lower than 1.1.15 (for example, 1.1.14, 1.1.0, or any version beginning with 1.0 or 1.1.x below 1.1.15)
-
Verify the Confluence user authentication settingsCheck whether Confluence allows anonymous or self-registered user access, as the vulnerability can be exploited with or without authenticationAffected if Anonymous access is enabled or the Confluence instance is exposed to untrusted users
-
Inspect access logs for suspicious file path requestsReview Confluence or web server logs for requests to API endpoints containing path traversal patterns such as '../' or absolute file paths (for example, ../../../../etc/passwd)Affected if Such patterns appear in the logs targeting the Zabbix plugin endpoints
-
Check for unauthorized file access indicatorsExamine server filesystem permissions and recent access logs for any unexpected reads of sensitive system files (like /etc/passwd, configuration files) that coincide with the plugin's availabilityAffected if Sensitive files were accessed during periods when the vulnerable plugin was exposed
A Confluence instance is affected if the MESILAT Zabbix plugin is installed with a version lower than 1.1.15 and is accessible to users (authenticated or anonymous).
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.1.15
Upgrade the MESILAT Zabbix plugin to version 1.1.15 or later to obtain the patched code. If the plugin is unused, consider removing it entirely to reduce the attack surface.
Fix this in Zabbix
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18289 — 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-18289 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