dbcve.org
GaroonApplication · Cybozu

CVE-2026-22881

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-02
Fix available
A fix is available. Upgrade to 6.0.3 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 exists in Message function of Cybozu Garoon 5.15.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 Message function of Cybozu Garoon versions 5.15.0 through 6.0.3 allows injection of malicious scripts, which can potentially be chained with session hijacking or CSRF to trigger unauthorized password resets for arbitrary users.

MitigationApply vendor-supplied patch or upgrade to a fixed version beyond 6.0.3; implement output encoding and input validation on the Message function and all password reset endpoints.

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.15.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
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. Confirm Cybozu Garoon installation
    Access the Garoon administration panel or check system inventory for Cybozu Garoon product. The application typically runs on web servers and can be identified by accessing the login portal at your Garoon URL.
    Affected if Cybozu Garoon is not installed, this CVE does not apply.
  2. Identify installed Garoon version
    Log into Garoon as an administrator, navigate to System Settings > System Information, or check version files such as version.ini, garoon/version, or the admin portal's system information page. The version is typically displayed in the format x.y.z.
    Affected if Unable to determine the version indicates the product may not be Garoon or access is insufficient.
  3. Verify version falls within affected range
    Compare your installed version against the vulnerable range: versions 5.15.0 through 6.0.3 (excluding 6.0.3). For example, versions 5.15.0, 5.15.1, 5.16.0, 5.17.0, 6.0.0, 6.0.1, and 6.0.2 are all affected.
    Affected if Your installed version is >= 5.15.0 and < 6.0.3, meaning the environment is within the vulnerable version range.
  4. Confirm Message function is accessible
    Verify the Message (Messaging) module is enabled and accessible within Garoon. Check under System Settings > Application settings > Messaging, or confirm regular users have access to the Message function through their portal.
    Affected if The Message function is enabled and users can compose or receive messages, making the XSS injection point accessible.

You are affected if Cybozu Garoon version is 5.15.0 or higher but lower than 6.0.3 and the Message function is 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

Apply vendor-supplied patch or upgrade to a fixed version beyond 6.0.3; implement output encoding and input validation on the Message function and all password reset endpoints.

Recommended fix High confidence

Garoon 6.0.3

  1. 1. Back up your current Garoon database and configuration files.
  2. 2. Download Garoon version 6.0.3 from the official Cybozu download portal or your contract page.
  3. 3. Review the Garoon upgrade documentation for your current version.
  4. 4. Stop the Garoon service before beginning the upgrade.
  5. 5. Run the upgrade installer for Garoon 6.0.3.
  6. 6. Verify the upgrade completed successfully by checking the system version.
  7. 7. Test the Message function to confirm the XSS vulnerability is remediated.
  8. 8. Restart the Garoon service.
Caveat Review Cybozu Garoon 6.0.3 release notes for any functional changes between your current version and 6.0.3

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 / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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