GroupsessionApplication

CVE-2025-61987

MEDIUM · 5.3 CVSS v3.0 Published 2025-12-12
Fix available
A fix is available. Upgrade to 5.3.0 / 5.3.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
GroupSession Free edition prior to ver5.3.0, GroupSession byCloud prior to ver5.3.3, and GroupSession ZION prior to ver5.3.2. do not validate origins in WebSockets. If a user accesses a crafted page, Chat information sent to the user may be exposed.

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 confidence

GroupSession versions prior to 5.3.0 (Free), 5.3.3 (byCloud), and 5.3.2 (ZION) fail to validate the Origin header during WebSocket handshake. This Cross-Site WebSocket Hijacking (CSWSH) vulnerability allows an attacker to establish authenticated WebSocket connections on behalf of a victim user, potentially exposing chat messages sent to that user.

MitigationUpgrade GroupSession to version 5.3.0+ (Free), 5.3.3+ (byCloud), or 5.3.2+ (ZION). If immediate patching is not possible, consider restricting WebSocket endpoints to trusted origins at the application or network level.

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
GroupsessionApplication
Affected:< 5.3.0< 5.3.2< 5.3.3

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed GroupSession version
    Check the version displayed in the GroupSession admin interface under 'System Information' or examine the WAR file name/version in the deployment directory
    Affected if The version is below 5.3.0 for Free edition, below 5.3.2 for ZION, or below 5.3.3 for byCloud
  2. Confirm WebSocket functionality is in use
    Review server logs or network traffic for WebSocket connection attempts to paths such as /gsapi/ws, /api/ws, or similar WebSocket endpoints used by GroupSession chat or messaging features
    Affected if WebSocket connections are being made to GroupSession, indicating the vulnerable handshake is occurring
  3. Test WebSocket handshake for Origin validation
    Send a WebSocket handshake request to the GroupSession WebSocket endpoint with an arbitrary Origin header (e.g., Origin: https://malicious-site.com) and observe whether the server accepts the handshake
    Affected if The server accepts the WebSocket handshake from an untrusted Origin, confirming the lack of Origin header validation
  4. Inspect application-level Origin configuration
    Check GroupSession configuration files (such as web.xml, server.xml, or any custom filter configurations) for any Origin or CORS-related validation settings on WebSocket endpoints
    Affected if No Origin validation filter or configuration is found for WebSocket endpoints

If GroupSession version is below 5.3.0/5.3.2/5.3.3 and WebSocket endpoints accept connections from arbitrary Origin headers, the environment is vulnerable to CSWSH attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.3.0 / 5.3.2 / 5.3.3 or later
Fixed in 5.3.05.3.25.3.3
Interim mitigation

Upgrade GroupSession to version 5.3.0+ (Free), 5.3.3+ (byCloud), or 5.3.2+ (ZION). If immediate patching is not possible, consider restricting WebSocket endpoints to trusted origins at the application or network level.

Recommended fix High confidence

GroupSession Free: 5.3.0+; ZION: 5.3.2+; byCloud: 5.3.3+

  1. 1. Identify the GroupSession product variant in use (Free edition, ZION, or byCloud)
  2. 2. For GroupSession Free edition: upgrade to version 5.3.0 or later
  3. 3. For GroupSession ZION: upgrade to version 5.3.2 or later
  4. 4. For GroupSession byCloud: upgrade to version 5.3.3 or later
  5. 5. After upgrade, verify that WebSocket connections properly validate origin headers

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Groupsession Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61987 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61987 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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