dbcve.org
Group OfficeApplication

CVE-2025-53505

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-21
Fix available
A fix is available. Upgrade to 6.8.119 / 25.0.20 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 path traversal vulnerability. If this vulnerability is exploited, information on the server hosting the product may be exposed.

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 path traversal vulnerability that allows attackers to access files outside the intended web directory, potentially exposing sensitive server configuration and system files.

MitigationUpgrade Group-Office to version 6.8.119 or later, or version 25.0.20 or later. Verify the upgrade in a non-production environment before deploying to production.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Identify Group-Office installation
    Search for Group-Office files in common web directories (e.g., /var/www/html/, /opt/groupoffice/, or the webroot used by your web server). Look for groupoffice.php, index.php, or a 'groupoffice' directory.
    Affected if Group-Office software is present on the server
  2. Determine installed Group-Office version
    Check the version file or configuration. Common locations include a version.php file in the root directory, or check the database configuration for version metadata. Run: find /path/to/webroot -name 'version.php' -o -name 'defaults.php' 2>/dev/null and inspect for version strings.
    Affected if The installed version is less than 6.8.119, or between 25.0.1 and 25.0.19 inclusive
  3. Verify web server serves Group-Office
    Confirm that the web server (Apache, Nginx, or IIS) is configured to serve the Group-Office directory. Check web server configuration files (httpd.conf, nginx.conf, or site configs) for aliases or document root pointing to Group-Office.
    Affected if Group-Office is accessible via HTTP/HTTPS requests
  4. Check for path traversal accessible endpoints
    Review web server access logs for unusual requests containing '../' sequences targeting Group-Office endpoints. Common path traversal indicators: requests with '..' URL encoded or raw patterns reaching system directories.
    Affected if Suspicious traversal patterns appear in logs or the vulnerable endpoint is accessible without authentication

A system is affected if Group-Office version is less than 6.8.119 or falls between 25.0.1 and 25.0.19, and the web interface is publicly or internally accessible.

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 later, or version 25.0.20 or later. Verify the upgrade in a non-production environment before deploying to production.

Recommended fix Moderate confidence

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

  1. 1. Back up your current Group Office installation and database before upgrading.
  2. 2. Determine your current major version branch (6.x or 25.x).
  3. 3. If running 6.x version: upgrade to version 6.8.119 or later.
  4. 4. If running 25.x version: upgrade to version 25.0.20 or later.
  5. 5. Download the appropriate fixed version from the official Group Office website (www.group-office.com).
  6. 6. Follow the official Group Office upgrade documentation for your version to complete the installation.
  7. 7. After upgrade, verify the installation and test that core functionality works correctly.

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

Fix this in Group Office Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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