CVE-2022-30604
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 the specific parameters of Cybozu Office 10.0.0 to 10.8.5 allows a remote 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 confidenceCross-site scripting (XSS) vulnerability in Cybozu Office versions 10.0.0 through 10.8.5 allows remote attackers to inject arbitrary JavaScript or HTML via specific parameters that are not properly sanitized or validated before being rendered in the application's web interface.
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>= 10.0.0, <= 10.8.5CVSS 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.
-
Confirm Cybozu Office is installedCheck for Cybozu Office by reviewing installed applications on the server, typically found in the web server's document root or application directory (commonly under /var/www/html/, /opt/, or C:\inetpub\ on Windows). Look for the 'office' directory or.cybozu.com related folders.Affected if Cybozu Office application files exist on the system
-
Locate the installed versionAccess the Cybozu Office system administrator settings page, or check the version information file typically located in the installation directory. The version may also be visible in the login page footer or system administration panel under 'System information' or 'Version info'.Affected if The version displayed cannot be determined or is not visible
-
Compare your version to the affected rangeVerify the installed version against the affected range: 10.0.0 through 10.8.5. If the detected version is 10.0.0, 10.0.1, 10.1.0, 10.2.0, 10.3.0, 10.4.0, 10.5.0, 10.6.0, 10.7.0, 10.8.0, 10.8.1, 10.8.2, 10.8.3, 10.8.4, or 10.8.5, the system is within the vulnerable range.Affected if The installed version is 10.0.0 to 10.8.5 inclusive
-
Identify accessible web endpointsReview web access logs or network configuration to confirm the Cybozu Office web interface is accessible to users. The XSS flaw requires the web interface to be reachable since it exploits parameters passed through HTTP requests.Affected if The web interface is accessible externally or to untrusted users
If Cybozu Office is installed with a version between 10.0.0 and 10.8.5 inclusive and its web interface is accessible, the environment is vulnerable to CVE-2022-30604.
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.
dbcve · scopedApply the vendor patch (Cybozu Office 10.8.6 or later) to properly encode output and sanitize user-supplied input in the affected parameters.
Cybozu Office 10.8.6 or later
- Identify the current Cybozu Office version installed in your environment
- Check Cybozu's official security advisory page (cs.cybozu.co.jp) or JVN (jvn.jp) for the specific fixed version number
- Upgrade Cybozu Office to the fixed version (version 10.8.6 or later based on typical Cybozu patch cadence)
- After upgrading, verify the fix by testing the previously affected parameters for XSS vulnerability
- Ensure proper testing is completed before deploying to production environments
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30604 — 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-30604 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