Authenticated browser script execution via stored XSS
Published Feb 1, 2024 · Updated Jun 4, 2025
Stored XSS in GroupOffice before 6.6.182, 6.7.64, or 6.8.31 lets remote authenticated users run scripts in a logging-in user’s browser. The application stores attacker-controlled input and later renders it without adequate neutralization, but public records do not identify the input field or code locus. A valid low-privilege account and interaction by a separate logging-in user are required, bounding the effect to that user’s browser session and accessible data or actions.
Summary
What happened
Stored XSS in GroupOffice before 6.6.182, 6.7.64, or 6.8.31 lets remote authenticated users run scripts in a logging-in user’s browser. The application stores attacker-controlled input and later renders it without adequate neutralization, but public records do not identify the input field or code locus. A valid low-privilege account and interaction by a separate logging-in user are required, bounding the effect to that user’s browser session and accessible data or actions.
The record
- CVE
- CVE-2024-23941
- Published
- Feb 1, 2024
- Updated
- Jun 4, 2025
- Vendor
- Intermesh BV
- Product
- GroupOffice
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 1, 2024CVE publishedPublication date reported by the CVE source.
- Jun 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=prior to v6.6.182
- Affected versionversion=prior to v6.7.64
- Affected versionversion=prior to v6.8.31
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo