CVE-2018-0559
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 vulnerability in Cybozu Mailwise 5.0.0 to 5.4.1 allows remote attackers to inject arbitrary web script or HTML 'Address' via unspecified vectors.
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 · moderate confidenceThis is a reflected cross-site scripting (XSS) vulnerability in Cybozu Mailwise versions 5.0.0 through 5.4.1. Attackers can inject malicious JavaScript or HTML into the 'Address' field, which gets executed in the browser of users who interact with the affected component. The CVSS 6.1 score indicates the attack requires some form of user interaction or social engineering.
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>= 5.0.0, <= 5.4.1CVSS 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 Cybozu Mailwise installationLocate and identify the Cybozu Mailwise application in your environment - check installed software listings, application directories, or system inventory records.Affected if Cybozu Mailwise is present on the system
-
Check installed version against affected rangeRetrieve the exact version number of the installed Cybozu Mailwise instance. This is typically found in the product's about page, version information, or installation logs. Compare it to the affected range 5.0.0 through 5.4.1.Affected if The installed version is 5.0.0, 5.4.1, or any version in between those values
-
Verify Address feature is accessibleDetermine whether the 'Address' functionality in Mailwise is enabled and accessible to users. This may involve checking user permissions, feature flags, or configuration settings within the application.Affected if The Address feature is enabled and users can access it to create or manage contacts
-
Inspect Address field for existing malicious contentReview any existing entries in the Address component of Mailwise, particularly fields that accept user-supplied names or addresses, for suspicious script tags or HTML markup that may indicate prior exploitation.Affected if The Address field contains unsanitized script or HTML tags that could execute in a user's browser
You are affected if Cybozu Mailwise versions 5.0.0 through 5.4.1 is installed, the Address feature is enabled, and users can input or view data in the Address field.
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 dataApply vendor-supplied patches for Cybozu Mailwise to version 5.4.2 or later. As a temporary workaround, disable or restrict access to the affected 'Address' functionality until patching is possible, and implement input validation and output encoding on all user-supplied data.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0559 — 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-0559 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