dbcve.org
GaroonApplication · Cybozu

CVE-2026-20711

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-02
Fix available
A fix is available. Upgrade to 6.0.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 exists in E-mail function of Cybozu Garoon 5.0.0 to 6.0.3, which may allow an attacker to reset arbitrary users’ passwords.

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

Cross-site scripting (XSS) vulnerability in the E-mail function of Cybozu Garoon versions 5.0.0 through 6.0.3 allows injection of malicious scripts. Successful exploitation can lead to manipulation of password reset flows, potentially enabling attackers to reset arbitrary user passwords.

MitigationUpgrade to a patched version of Cybozu Garoon; if no patch available, sanitize all email function inputs, implement output encoding, and consider disabling the email function until resolved.

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:>= 5.0.0, < 6.0.3

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/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 checks

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

  1. Verify Cybozu Garoon is installed
    Identify the installed application - confirm it is Cybozu Garoon by checking the product name in the system information or administration console
    Affected if The application is not Cybozu Garoon, then this CVE does not apply
  2. Check installed version
    Access the system administration panel or version information page to determine the exact version number of Cybozu Garoon
    Affected if The version is 5.0.0 or higher but lower than 6.0.3 - this indicates the environment falls within the affected range
  3. Confirm E-mail function is enabled
    Navigate to the system settings or module configuration in the administration console and verify whether the E-mail function module is active and accessible to users
    Affected if The E-mail function is enabled and accessible - this is the specific component where the XSS vulnerability exists
  4. Verify user access to password reset flows
    Check if standard users have access to password reset functionality through the E-mail function, which is the attack vector for password manipulation
    Affected if Users can access password reset via email - combined with the vulnerable version and enabled email function, this creates the exploitation path described in the CVE

The environment is affected if Cybozu Garoon version is between 5.0.0 and 6.0.3 inclusive and the E-mail function is enabled and accessible to users.

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 6.0.3 or later
Fixed in 6.0.3
Interim mitigation

Upgrade to a patched version of Cybozu Garoon; if no patch available, sanitize all email function inputs, implement output encoding, and consider disabling the email function until resolved.

Recommended fix Moderate confidence

Garoon 6.0.3 or later

  1. 1. Back up the current Garoon installation and database before proceeding with any upgrade.
  2. 2. Download the latest version of Garoon (6.0.3 or later) from the official Cybozu download page or your licensed distribution channel.
  3. 3. Review the Garoon upgrade guide for version 6.0.3 to ensure all prerequisites are met.
  4. 4. Stop the Garoon service before beginning the upgrade process.
  5. 5. Run the upgrade installer for Garoon 6.0.3 or later.
  6. 6. Verify the upgrade was successful by checking the Garoon administration screen.
  7. 7. Test the E-mail function to confirm the XSS vulnerability has been remediated.
  8. 8. Inform users to clear their browser caches after the upgrade.
Caveat Review Cybozu's upgrade notes for version 6.0 for any configuration or compatibility changes from version 5.x

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

Fix this in Garoon Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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