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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6.8.172, 25.0.108, 26.0.33
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Attacker needs an account that can create manual reminders (default for all users) Victim's browser must poll for pending notifications (checkForNotifications) so the payload renders
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Attacker needs an account that can create manual reminders (default for all users) Victim's browser must poll for pending notifications (checkForNotifications) so the payload rendersUpgrade to a fixed version: 6.8.172, 25.0.108, 26.0.33.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Intermesh groupoffice
fixed in 6.8.172; fixed in 25.0.108; fixed in 26.0.33
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-63010
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: cve.now feed data
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: github.com
Which versions are affected by CVE-2026-63010?
groupoffice: before 6.8.172; before 25.0.108; before 26.0.33.Source: cve.now feed data
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: github.com
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: github.com