dbcve.org
Group OfficeApplication · Intermesh

CVE-2026-27832

HIGH · 8.8 CVSS v3.1 Published 2026-02-27
Fix available
A fix is available. Upgrade to 6.8.153 / 25.0.87 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 is an enterprise customer relationship management and groupware tool. Versions prior to 26.0.8, 25.0.87, and 6.8.153 have a SQL Injection (SQLi) vulnerability, exploitable through the `advancedQueryData` parameter (`comparator` field) on an authenticated endpoint. The endpoint `index.php?r=email/template/emailSelection` processes `advancedQueryData` and forwards the SQL comparator without a strict allowlist into SQL condition building. This enables blind boolean-based exfiltration of the `core_auth_password` table. Versions 26.0.8, 25.0.87, and 6.8.153 fix the issue.

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 confidence

SQL injection in the `advancedQueryData` parameter's comparator field on the authenticated endpoint `index.php?r=email/template/emailSelection` allows blind boolean-based exfiltration of the `core_auth_password` table. The SQL comparator is forwarded without strict allowlist validation into SQL condition building.

MitigationUpgrade to versions 26.0.8, 25.0.87, or 6.8.153 to apply the patch that implements strict allowlisting for the comparator field.

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.153>= 25.0.1, < 25.0.87>= 26.0.1, < 26.0.8

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 installed Group Office version
    Check the version number in the Group Office administration panel under 'System' > 'About' or inspect the version file in the installation directory (typically version.php or similar)
    Affected if The installed version is < 6.8.153 OR >= 25.0.1 AND < 25.0.87 OR >= 26.0.1 AND < 26.0.8
  2. Verify the vulnerable endpoint exists
    Confirm the file index.php exists in the web root and the 'email/template/emailSelection' route is accessible in the application routing
    Affected if The endpoint index.php?r=email/template/emailSelection is present in the application
  3. Confirm authentication is enabled
    Check that the application requires login and user accounts exist in the system
    Affected if User authentication is configured and the application accepts logins
  4. Check for recent SQL injection indicators
    Review web server access logs for unusual queries targeting the 'advancedQueryData' parameter, particularly patterns containing 'core_auth_password' or SQL operators in the comparator field
    Affected if Log entries show requests to emailSelection with abnormal SQL-like patterns in advancedQueryData parameter

A user is affected if they run any version of Intermesh Group Office within the ranges < 6.8.153, >= 25.0.1 to < 25.0.87, or >= 26.0.1 to < 26.0.8 AND the application has authenticated users who can access the email template selection endpoint.

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.153 / 25.0.87 / 26.0.8 or later
Fixed in 6.8.15325.0.8726.0.8
Interim mitigation

Upgrade to versions 26.0.8, 25.0.87, or 6.8.153 to apply the patch that implements strict allowlisting for the comparator field.

Recommended fix High confidence

Upgrade to 6.8.153 for legacy versions; upgrade to 25.0.87 for 25.x versions; upgrade to 26.0.8 for 26.x versions

  1. Identify the currently installed Group Office version by checking the administration panel or version file
  2. Determine the appropriate upgrade path based on current version: if < 6.8.153 upgrade to 6.8.153; if >= 25.0.1 and < 25.0.87 upgrade to 25.0.87; if >= 26.0.1 and < 26.0.8 upgrade to 26.0.8
  3. Backup the Group Office database and all application files before proceeding with the upgrade
  4. Download the official Group Office upgrade package from the vendor (refer to official documentation at group-office.com)
  5. Follow the official upgrade instructions for your deployment method (manual upload or package manager)
  6. Test the upgrade in a non-production environment first to verify functionality
  7. Deploy the upgrade to production after successful testing
  8. Verify the installed version matches the expected fixed version (6.8.153, 25.0.87, or 26.0.8)

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
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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