CVE-2024-23941
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 · uneditedCross-site scripting vulnerability exists in Group Office prior to v6.6.182, prior to v6.7.64 and prior to v6.8.31, which may allow a remote authenticated attacker to execute an arbitrary script on the web browser of the user who is logging in to the product.
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 · moderate confidenceA stored cross-site scripting (XSS) vulnerability in Group Office versions prior to v6.6.182, v6.7.64, and v6.8.31 allows authenticated attackers to inject malicious scripts that execute in the browser of users logging into the system. The vulnerability likely resides in user-supplied input within the login or user profile flow that is insufficiently sanitized before being rendered back to users.
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< 6.6.182>= 6.7.0, < 6.7.64>= 6.8.0, < 6.8.31CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Group Office version numberAccess the Group Office admin panel (typically at /admin or /site.php?admin=1) and navigate to the System Information or About page. Alternatively, check the version.php file in the Group Office root directory or the config.php file for a version entry.Affected if The version displayed is below 6.6.182, between 6.7.0 and 6.7.63, or between 6.8.0 and 6.8.30.
-
Identify the installed Group Office version via command lineIf you have shell access, check the composer.json file in the Group Office installation directory for the 'version' or 'groupoffice/version' entry, or run a package manager query such as 'composer show groupoffice/groupoffice' if installed via Composer.Affected if The reported version falls within the affected ranges listed above.
-
Inspect user profile fields for injected scriptsLog in as an administrator and navigate to the user management section. Review all user profile fields including display name, email signature, and custom fields for suspicious content such as <script> tags, javascript: URIs, or event handlers like onload, onerror, or onmouseover.Affected if Any user profile field contains HTML script tags or JavaScript code that could execute upon user login.
-
Examine the login page and user creation formsReview the HTML source of the login page and user creation/editing forms in your browser developer tools. Look for any user-supplied data that is reflected back without proper encoding, particularly in areas that display the logged-in user's information.Affected if User-supplied input such as username or display name appears in the page source unescaped or with HTML tags intact.
-
Check browser console for XSS errors or unexpected script executionLog into Group Office using a test account and open the browser developer console (F12). Look for any script execution errors, unexpected network requests to external domains, or JavaScript code executing that was not authored by your organization.Affected if Scripts execute automatically on login or user profile display without explicit user action, or console shows references to unfamiliar JavaScript files.
Your Group Office installation is affected if its version is below 6.6.182, between 6.7.0-6.7.63, or between 6.8.0-6.8.30, or if you observe unescaped script content in user profile fields or unexpected script execution in the browser upon login.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.6.1826.7.646.8.31
Upgrade to Group Office v6.6.182, v6.7.64, v6.8.31 or later. In the interim, disable or restrict user accounts that are not trusted and implement Content Security Policy (CSP) headers to mitigate XSS execution.
6.8.31 (latest stable fix; alternatively 6.7.64 or 6.6.182 depending on your version branch)
- Identify your current Group Office version by checking the admin panel or installation directory
- Determine which version branch you are running (6.6.x, 6.7.x, or 6.8.x)
- For 6.6.x users: Upgrade to version 6.6.182 or later
- For 6.7.x users: Upgrade to version 6.7.64 or later
- For 6.8.x users: Upgrade to version 6.8.31 or later
- After upgrading, clear browser cache and test the login functionality
- Verify the XSS vulnerability is remediated by logging in and confirming no script execution occurs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23941 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23941 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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