CVE-2025-48366
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 · uneditedGroup-Office is an enterprise customer relationship management and groupware tool. Prior to versions 6.8.119 and 25.0.20, a stored and blind XSS vulnerability exists in the Phone Number field of the user profile within the GroupOffice application. This allows a malicious actor to inject persistent JavaScript payloads, which are triggered in the context of another user when they view the Address Book. Successful exploitation enables actions such as forced redirects, unauthorized fetch requests, or other arbitrary JavaScript execution without user interaction. Versions 6.8.119 and 25.0.20 contain a fix for the issue.
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 · high confidenceA stored XSS vulnerability in the Phone Number field of Group-Office user profiles allows malicious JavaScript payloads to persist and execute when other users view the Address Book. The 'blind' nature means the attacker doesn't directly see the response, but the payload runs in the victim's browser context enabling forced redirects, unauthorized fetch requests, or other arbitrary JavaScript execution.
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.8.199>= 25.0.1, < 25.0.20CVSS 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.
-
Identify the installed Group-Office versionLocate the version file or admin panel about page that displays the current Group-Office version numberAffected if The version is less than 6.8.199 or falls between 25.0.1 and 25.0.19 inclusive
-
Confirm the Address Book module is accessibleVerify that users can access the Address Book feature which displays user profile information including phone numbersAffected if The Address Book module is enabled and accessible to users
-
Inspect phone number fields in user profilesNavigate to user profile settings or the Address Book and examine the Phone Number field for any unexpected characters, tags, or script-like contentAffected if The phone number field contains HTML, JavaScript tags, or encoded script payloads
-
Check for existing malicious payloads in the databaseQuery the database tables storing user profile data (such as contacts or users tables) for XSS patterns in phone number fieldsAffected if Database contains script tags, event handlers, or suspicious encoded content in phone number columns
-
Review recent user profile modificationsExamine audit logs or user profile modification history for unexpected changes to phone number fieldsAffected if Phone number fields were recently modified with unusual content or mass updates occurred
A user is affected if their Group-Office version is below 6.8.199 or between 25.0.1-25.0.19, the Address Book is active, and phone number fields contain or can store unsanitized HTML/JavaScript content.
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.8.19925.0.20
Upgrade Group-Office to version 6.8.119 or 25.0.20 which contains the fix for this stored XSS in the phone number field.
Group Office 6.8.119 or later for 6.x users; Group Office 25.0.20 or later for 25.x users
- 1. Identify the currently installed Group Office version by checking the administration panel or system information
- 2. If running version 6.x (less than 6.8.119), plan upgrade to version 6.8.119 or later
- 3. If running version 25.x (between 25.0.1 and 25.0.19), plan upgrade to version 25.0.20 or later
- 4. Before upgrading, backup the database and application files
- 5. Review upgrade documentation for your specific version branch for any prerequisites
- 6. Perform the upgrade following vendor's standard upgrade procedure
- 7. After upgrade, verify the phone number field now properly sanitizes input
- 8. Confirm the fix by attempting to create a test user with special characters in the phone field and verifying it does not execute
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48366 — 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-2025-48366 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