CVE-2019-5937
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 4.0.0 to 4.10.1 allows remote authenticated attackers to inject arbitrary web script or HTML via the user information.
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 confidenceStored XSS vulnerability in Cybozu Garoon allows authenticated users to inject malicious scripts/HTML through user information fields. The vulnerability affects versions 4.0.0 through 4.10.1 and can be exploited by any authenticated user modifying their own user profile information.
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>= 4.0.0, <= 4.10.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Verify Cybozu Garoon installationCheck for Garoon installation directories or running web services on common ports (e.g., /var/www/html/, /opt/cybozu/, or look for garoon.exe on Windows). Alternatively, check system services or web server configurations for Garoon instances.Affected if Cybozu Garoon software is present on the system
-
Determine installed Garoon versionLocate the version information in the Garoon installation: check the version file (often version.xml or similar in the installation directory), the Garoon administrator login page footer, or query the system via Garoon's API if accessible.Affected if Installed version falls within 4.0.0 through 4.10.1 inclusive
-
Confirm user profile functionality is accessibleLog into Garoon as an authenticated user and navigate to the user profile settings section (typically under personal settings or user information). Verify that the ability to edit user information fields is available.Affected if Authenticated users can access and modify their own user profile information fields
-
Check for indicators of exploitation in logsReview Garoon access logs and application logs for suspicious patterns in user information fields, such as script tags (<script>), javascript: URIs, or HTML tags in fields that should contain plain text (e.g., user name, organization, phone fields).Affected if Logs contain unexpected HTML, script tags, or event handler attributes in user profile-related fields
The environment is affected if Cybozu Garoon versions 4.0.0 through 4.10.1 are installed and the user profile modification feature is 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 dataApply vendor patch or upgrade to Cybozu Garoon version 4.10.2 or later which addresses this XSS vulnerability in user information handling.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5937 — 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-2019-5937 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