CVE-2024-31401
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 5.0.0 to 5.15.2 allows a remote authenticated attacker with an administrative privilege to inject an arbitrary script on the web browser of the user who is logging in to the product.
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 5.0.0 through 5.15.2 allows an authenticated attacker with administrative privileges to inject arbitrary JavaScript that executes in the browsers of users logging into the product.
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.5.0, < 6.0.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
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 is installedLocate the Garoon installation directory or check system services for 'Garoon' processes. On Windows, check Program Files; on Linux, check /opt/ or /var/lib/.Affected if Cybozu Garoon software is present on the system
-
Check installed Garoon versionAccess the Garoon system information page (typically /g/ on the web interface) or check the version file in the installation directory. The version is displayed on the login page footer or in the administration panel under 'System Settings' > 'System Information'.Affected if The displayed version falls within 5.5.0 through 5.15.2 (any version >= 5.5.0 and < 6.0.0)
-
Verify administrative interface is enabledLog into Garoon as a system administrator and confirm access to the 'System Administration' panel. Check if the /g/admin/ path is accessible.Affected if Administrative users exist and the admin panel is accessible (required condition for exploitation)
-
Inspect login page for user-controlled fieldsView the HTML source of the Garoon login page (typically /g/login). Look for input fields that might reflect values without proper encoding.Affected if User-supplied input in login-related forms is reflected in the page without sanitization
You are affected if Cybozu Garoon version 5.5.0 through 5.15.2 is installed AND administrative users can access the admin panel, as the XSS requires admin privileges to inject the malicious script.
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.
dbcve · scoped6.0.0
Upgrade Cybozu Garoon to version 5.15.3 or later to obtain the vendor patch for this vulnerability.
Garoon 6.0.0 or later
- Verify current Garoon version by accessing the system administration screen
- Schedule a maintenance window for the upgrade
- Backup the current Garoon database and configuration files
- Upgrade Garoon to version 6.0.0 or later following the official upgrade documentation
- After upgrade, verify the XSS vulnerability is resolved by checking that malicious scripts cannot be injected via administrative functions
- Confirm all users can log in successfully after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31401 — 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-2024-31401 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