dbcve.org
GaroonApplication · Cybozu

CVE-2021-20767

MEDIUM · 5.4 CVSS v3.1 Published 2021-08-18
Fix available
A fix is available. Upgrade to after 5.0.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Cross-site scripting vulnerability in Full Text Search of Cybozu Garoon 4.0.0 to 5.0.2 allows a remote authenticated attacker to inject an arbitrary script 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 · high confidence

Cross-site scripting (XSS) vulnerability in the Full Text Search component of Cybozu Garoon versions 4.0.0 through 5.0.2 allows authenticated remote attackers to inject malicious JavaScript code through unsanitized search input that gets reflected in search results.

MitigationApply vendor-supplied security patch for CVE-2021-20767; if unavailable, implement robust input validation and output encoding for all Full Text Search inputs and their displayed results.

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
GaroonApplication
Affected:>= 4.0.0, <= 5.0.2

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Cybozu Garoon version
    Access the system administration panel or check the Garoon version information page. On the administration screen, navigate to 'System Administration' > 'System Information' > 'Product Version' to view the exact version number installed.
    Affected if The installed version is >= 4.0.0 and <= 5.0.2
  2. Verify Full Text Search is enabled
    Check if the Full Text Search module is active in the Garoon configuration. Navigate to 'System Administration' > 'Application Settings' > 'Full Text Search' to see if the feature is turned on.
    Affected if Full Text Search is enabled and the version is within the affected range (4.0.0 to 5.0.2)
  3. Inspect search result output for XSS indicators
    Log in as an authenticated user and perform a search using the Full Text Search function. Check the HTTP response and rendered page for any unescaped HTML or script tags in the search results display area.
    Affected if Search input is reflected in results without proper HTML encoding
  4. Review web server logs for XSS attack patterns
    Examine access logs and application logs for suspicious search queries containing JavaScript tags such as <script>, onerror, onload, or javascript: URIs submitted to the Full Text Search endpoint.
    Affected if Logs show XSS payload patterns in search queries from internal users

You are affected if Cybozu Garoon version 4.0.0 through 5.0.2 is installed AND the Full Text Search component is enabled, as the XSS flaw exists in that component's search input handling.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 5.0.2
Interim mitigation

Apply vendor-supplied security patch for CVE-2021-20767; if unavailable, implement robust input validation and output encoding for all Full Text Search inputs and their displayed results.

Recommended fix Moderate confidence

Garoon 5.0.3 or later (latest stable release)

  1. 1. Back up the current Garoon database and configuration files before starting the upgrade process.
  2. 2. Download the latest version of Garoon (version 5.0.3 or later) from the official Cybozu download page or your licensing portal.
  3. 3. Review the official Garoon upgrade guide for your current version to ensure compatibility requirements are met.
  4. 4. Stop the Garoon service on your server.
  5. 5. Run the Garoon installer/upgrade program following the on-screen instructions.
  6. 6. After upgrade completes, verify that the Full Text Search functionality is working correctly.
  7. 7. Test that the XSS vulnerability is remediated by verifying that user-supplied scripts cannot be executed in the Full Text Search feature.
  8. 8. Restart the Garoon service and verify all other core functionalities are operational.
Caveat Review release notes for your specific version jump - some customizations or integrations may require updates; minor version upgrades typically have lower compatibility risk but test thoroughly in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Garoon Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-20767 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-20767 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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