Skip to main content
CVE-2025-48993VulnerabilityPublished

CVE-2025-48993: Intermesh groupoffice · Cross-site Scripting

Affects Intermesh groupofficeSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium : upgrade to 25.0.27 or 6.8.123 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 25.0.27, 6.8.123
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade intermesh/groupoffice to 25.0.27 or 6.8.123.

Affected software

ProductAffectedFixed in
GitHubintermesh/groupofficepkg:github/intermesh/groupofficeOther threatsAffected
  • <6.8.123
  • <25.0.27
Fixed in
  • 6.8.123
  • 25.0.27

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate upgrade to Group-Office versions 6.8.123 or 25.0.27, where the vulnerability is patched, is the primary and most effective mitigation. 2. Implement strict Content Security Policy (CSP) headers on the web application to restrict the execution of unauthorized scripts and reduce the impact of potential XSS payloads. 3. Conduct a thorough review and hardening of all user input fields beyond the Look and Feel formatting fields to ensure comprehensive input validation and output encoding, following OWASP XSS prevention guidelines. 4. Monitor user activity logs for unusual changes to Look and Feel settings or other profile customizations that could indicate exploitation attempts. 5. Educate users about phishing and social engineering risks that could be used to trigger reflected XSS attacks. 6. Employ web application firewalls (WAFs) with updated signatures to detect and block malicious payloads targeting this vulnerability. 7. For organizations unable to immediately upgrade, consider temporarily restricting access to the Look and Feel customization features or limiting them to trusted administrators only. 8. Regularly scan and test the Group-Office deployment with automated vulnerability scanners and penetration testing to detect any residual or related issues.

Description

Group-Office is an enterprise customer relationship management and groupware tool. Prior to versions 6.8.123 and 25.0.27, a malicious JavaScript payload can be executed via the Look and Feel formatting fields. Any user can update their Look and Feel Formatting input fields, but the web application does not sanitize their input. This could result in a reflected cross-site scripting (XSS) attack. This issue has been patched in versions 6.8.123 and 25.0.27.

References

Community reviews

Loading reviews…