dbcve.org
Group OfficeApplication

CVE-2025-53504

MEDIUM · 5.4 CVSS v3.0 Published 2025-08-21
Fix available
A fix is available. Upgrade to 6.8.119 / 25.0.20 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
Group-Office versions prior to 6.8.119 and prior to 25.0.20 provided by Intermesh BV contain a cross-site scripting vulnerability. If this vulnerability is exploited, an arbitrary script may be executed in the 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 · moderate confidence

Group-Office versions prior to 6.8.119 and 25.0.20 contain a cross-site scripting (XSS) vulnerability that allows attackers to inject malicious scripts into web pages viewed by other users, potentially stealing session cookies or performing actions on behalf of authenticated users.

MitigationUpgrade Group-Office to version 6.8.119 or 25.0.20 or later to receive the security patch. If immediate patching is not possible, implement input validation and output encoding on user-supplied data.

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
Group OfficeApplication
Affected:< 6.8.119>= 25.0.1, < 25.0.20

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.0/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. Check Group-Office version in admin panel
    Log into the Group-Office admin panel and navigate to System > About or Settings > System Information to view the installed version number
    Affected if The displayed version is below 6.8.119 or is between 25.0.1 and 25.0.19 inclusive
  2. Check version via command line or config file
    Check the version file in the Group-Office installation directory, typically found in config.php or a version.php file within the /groupoffice/ directory
    Affected if The version number in the file is below 6.8.119 or falls within the 25.0.1 to 25.0.19 range
  3. Check HTTP server headers for version disclosure
    Send an HTTP request to the Group-Office server and inspect the Server header or X-Powered-By header for version information
    Affected if The headers reveal a version number that matches the affected ranges (< 6.8.119 or >= 25.0.1 and < 25.0.20)
  4. Verify user input fields are accessible
    Navigate to common user input areas such as the notes field, address book, email compose, or any custom field that accepts text input
    Affected if The application accepts and stores user-supplied text without visible immediate encoding (this confirms the attack surface exists)

If the installed version falls below 6.8.119 or is between 25.0.1 and 25.0.19, the environment is vulnerable to CVE-2025-53504 and user input processing is active.

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.8.119 / 25.0.20 or later
Fixed in 6.8.11925.0.20
Interim mitigation

Upgrade Group-Office to version 6.8.119 or 25.0.20 or later to receive the security patch. If immediate patching is not possible, implement input validation and output encoding on user-supplied data.

Recommended fix High confidence

6.8.119 (for 6.x releases) or 25.0.20 (for 25.x releases)

  1. 1. Identify the currently installed Group Office version by checking the system administration panel or version information.
  2. 2. If running a version < 6.8.119, plan upgrade to version 6.8.119 or later.
  3. 3. If running version >= 25.0.1 but < 25.0.20, plan upgrade to version 25.0.20 or later.
  4. 4. Review the official Group Office release notes/changelog for the target version to understand changes.
  5. 5. Perform a full backup of the Group Office database, files, and configuration before upgrading.
  6. 6. Test the upgrade in a staging/development environment first.
  7. 7. Apply the upgrade following the standard Group Office upgrade procedure for your deployment type.
  8. 8. After upgrade, verify the new version is correctly installed and the application functions normally.

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

Fix this in Group Office Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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