dbcve.org
GaroonApplication · Cybozu

CVE-2021-20769

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 Bulletin of Cybozu Garoon 4.6.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 · moderate confidence

This is a stored cross-site scripting (XSS) vulnerability in Cybozu Garoon's Bulletin function. An authenticated remote attacker can inject malicious JavaScript code into bulletin entries that will execute in the browsers of other users who view the affected content, potentially allowing session hijacking or data theft.

MitigationUpgrade to Cybozu Garoon version 5.0.3 or later which contains the patch. Until then, restrict bulletin creation permissions to trusted users only and implement Content Security Policy headers as a defense-in-depth measure.

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.6.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 Cybozu Garoon installation
    Locate the Garoon application in your environment - typically accessed via web browser at your organization's internal URL. Confirm the product name displays as Cybozu Garoon on the login or administration page.
    Affected if The product is Cybozu Garoon and the version falls within 4.6.0 through 5.0.2 inclusive.
  2. Determine installed Garoon version
    Access the administration panel or system information page within Garoon. The version is usually displayed under 'System Settings' or 'Product Information'. Compare your version number to the affected range of >= 4.6.0 and <= 5.0.2.
    Affected if Your installed version is 4.6.0, 4.6.1, 4.6.2, 4.6.3, 4.7.0, 4.8.0, 4.9.0, 4.10.0, 5.0.0, 5.0.1, or 5.0.2.
  3. Verify Bulletin function is accessible
    Log in as a standard user and navigate to the Bulletin board module (often labeled as 'Bulletin' or 'BBS' in the Garoon navigation menu). Confirm the module is active and users can view or create entries.
    Affected if The Bulletin function is enabled and users have access to create or view bulletin entries.
  4. Inspect bulletin entries for suspicious content
    Review existing bulletin posts, particularly those created by users with malicious intent. Look for abnormal script tags, JavaScript event handlers, or encoded payloads in the bulletin title or content fields.
    Affected if Any bulletin entries contain unsanitized HTML or JavaScript code that could execute in a user's browser.

You are affected if Cybozu Garoon version 4.6.0 through 5.0.2 is installed and the Bulletin module is active, allowing authenticated users to create content that could contain malicious scripts.

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

Upgrade to Cybozu Garoon version 5.0.3 or later which contains the patch. Until then, restrict bulletin creation permissions to trusted users only and implement Content Security Policy headers as a defense-in-depth measure.

Recommended fix Moderate confidence

Garoon 5.0.3 or later

  1. 1. Back up the current Garoon database and configuration files.
  2. 2. Download Garoon version 5.0.3 or later from the official Cybozu download portal.
  3. 3. Stop the Garoon service before applying the update.
  4. 4. Apply the upgrade following the standard Cybozu Garoon upgrade procedure.
  5. 5. Verify the Bulletin function works correctly after upgrade.
  6. 6. Test that the XSS vulnerability is remediated by attempting to inject script content in the Bulletin module.
Caveat Review release notes for any breaking changes between 5.0.x versions; standard upgrade precautions apply

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

Fix this in Garoon Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-20769 — 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-20769 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