CVE-2016-4906
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 Garoon 3.0.0 to 4.2.2 allows remote attackers to inject arbitrary web script or HTML via "Messages" function of Cybozu Garoon Keitai.
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 Cybozu Garoon versions 3.0.0 through 4.2.2 allows remote attackers to inject arbitrary JavaScript or HTML via the Messages function in the mobile (Keitai) interface. This is a stored XSS issue where malicious script persists and executes when other users view the compromised message.
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= 3.0.0= 3.0.1= 3.0.2= 3.0.3= 3.1.0= 3.1.1= 3.1.2= 3.1.3= 3.5.0= 3.5.1= 3.5.2= 3.5.3CVSS 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 Garoon installationAccess the web application's login page or check system documentation to identify if Cybozu Garoon is deployed. Look for the Cybozu Garoon login interface or check the HTTP server headers for 'Cybozu' or 'Garoon' identifiers.Affected if Cybozu Garoon is not present in the environment.
-
Identify installed Garoon versionLog into Garoon as an administrator. Navigate to System Settings > System Information > Product Version, or check the bottom of any Garoon page for the version number displayed.Affected if The installed version is 3.0.0 through 4.2.2 (including all patch versions within this range).
-
Verify Keitai mobile interface is enabledAccess the mobile interface by navigating to the Garoon URL with '/mobile/' or '/ktai/' path suffix from a mobile device or browser user-agent. Alternatively, check System Settings > General > Application Settings > Mobile for the 'Enable mobile interface' option.Affected if The mobile (Keitai) interface is accessible and enabled.
-
Confirm Messages function is available in mobile interfaceLog into the mobile interface and locate the Messages (メッセージ) function in the navigation menu. Check if users can create, view, or reply to messages via the mobile interface.Affected if The Messages function is accessible through the mobile interface.
-
Inspect stored messages for malicious contentAccess the Messages function via the standard web interface as an administrator. Browse through recent messages, particularly those created around the time of potential exploitation. View the message source or HTML to inspect for injected script tags, event handlers, or suspicious JavaScript URLs.Affected if Any message contains unsanitized HTML or script tags that could execute JavaScript when viewed.
The environment is affected if Cybozu Garoon version 3.0.0 through 4.2.2 is installed with the Keitai mobile interface and Messages function both enabled, regardless of whether malicious content is currently present.
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 dataUpgrade Cybozu Garoon to a version beyond 4.2.2 that includes the security patch. Until patched, restrict or disable the Messages function in the Keitai mobile interface for untrusted users.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4906 — 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-2016-4906 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