CVE-2022-27627
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 Organization's Information of Cybozu Garoon 4.10.2 to 5.5.1 allows a remote attacker to execute an arbitrary script on the logged-in user's web browser.
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 confidenceStored cross-site scripting (XSS) vulnerability in the Organization's Information feature of Cybozu Garoon versions 4.10.2 through 5.5.1 allows a remote attacker to inject malicious JavaScript into the Organization's Information field, which executes in the browsers of users who view this information.
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>= 4.10.2, <= 5.5.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Cybozu Garoon versionAccess the system administration panel or check the Garoon version through the help/about section. Common paths: /g/ or check the login page footer for version number.Affected if The installed version falls within 4.10.2 to 5.5.1 inclusive.
-
Confirm Organization's Information feature is in useNavigate to the system administration or organization management section where Organization's Information can be configured and viewed. Look for the Organization's Information module or settings.Affected if The Organization's Information feature is enabled or has been configured with data.
-
Review Organization's Information content for suspicious scriptsAccess the Organization's Information editor or viewer panel. Manually inspect all text fields for unexpected script tags, JavaScript event handlers (onerror, onload, onclick), or encoded characters that may contain XSS payloads.Affected if The Organization's Information contains unsanitized HTML, script tags, or JavaScript event handlers that could execute in a user's browser.
-
Check browser console for XSS errors when viewing organization infoAs a test user, navigate to view the Organization's Information page. Open the browser developer console and look for any script execution errors or unexpected behavior.Affected if JavaScript executes or errors appear when loading the Organization's Information page, indicating injected code is running.
You are affected if your Cybozu Garoon version is between 4.10.2 and 5.5.1 inclusive and the Organization's Information feature contains malicious script content.
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.
From vendor dataApply the vendor security patch to update Cybozu Garoon to a version newer than 5.5.1, or implement input validation and output encoding on the Organization's Information input fields to sanitize user-supplied content.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27627 — 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-2022-27627 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