dbcve.org
OfficeApplication · Cybozu

CVE-2022-28715

MEDIUM · 6.1 CVSS v3.1 Published 2022-08-18
Fix available
A fix is available. Upgrade to after 10.8.5 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 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 confidence

Cross-site scripting (XSS) vulnerability in Cybozu Office versions 10.0.0 through 10.8.5 allows remote attackers to inject arbitrary JavaScript or HTML into specific parameters. This occurs due to insufficient input validation or improper output encoding in the affected parameters, enabling script execution in the context of a victim's browser session.

MitigationApply the vendor patch (Cybozu Office 10.8.6 or later). Until patched, implement output encoding and input validation on all user-supplied parameters in affected areas, and consider deploying WAF rules as an interim control.

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
OfficeApplication
Affected:>= 10.0.0, <= 10.8.5

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. Confirm Cybozu Office installation
    Locate the Cybozu Office installation by checking for the application directory, typically under the web server's document root or the Cybozu installation folder. Look for the main executable or service running on the expected port (usually port 80/443 or a configured port).
    Affected if Cybozu Office is installed and running on the system
  2. Identify installed Cybozu Office version
    Access the Cybozu Office version information through the administrative interface (usually under 'System Settings' > 'Version Information' or similar), or check the version file in the installation directory if accessible. The version is typically displayed in the login page footer or in the system information panel.
    Affected if The installed version falls within 10.0.0 through 10.8.5
  3. Verify the application is exposed to network
    Confirm that the Cybozu Office web interface is accessible from network positions where untrusted users could submit requests. Check firewall rules and access control lists that permit HTTP/HTTPS traffic to the Cybozu Office server.
    Affected if The application is network-accessible to remote attackers who can submit crafted requests

A user is affected if Cybozu Office version 10.0.0 through 10.8.5 is installed and network-accessible, as this allows remote attackers to inject malicious scripts via specific parameters.

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 10.8.5
Interim mitigation

Apply the vendor patch (Cybozu Office 10.8.6 or later). Until patched, implement output encoding and input validation on all user-supplied parameters in affected areas, and consider deploying WAF rules as an interim control.

Recommended fix Moderate confidence

Upgrade to Cybozu Office version 10.9.0 or later (any release after 10.8.5)

  1. 1. Identify the current installed version of Cybozu Office by accessing the system administration settings or checking the product version information.
  2. 2. Schedule a maintenance window for the upgrade process to minimize business impact.
  3. 3. Back up all critical data, including the database and configuration files, before performing the upgrade.
  4. 4. Obtain the latest stable version of Cybozu Office from the official vendor (Cybozu) - the fixed version is any release after 10.8.5.
  5. 5. Follow the vendor's official upgrade documentation to apply the update.
  6. 6. After upgrade, verify the installation was successful and test that the application functions normally.
  7. 7. Confirm the vulnerability is remediated by checking that the specific XSS vector can no longer be exploited.
Caveat Review vendor release notes for any configuration or feature changes between your current version and the target version

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

Fix this in Office 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-2022-28715 — 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-2022-28715 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