dbcve.org
SysreptorApplication · Syslifters

CVE-2024-36076

HIGH · 8.8 CVSS v3.1 Published 2024-05-19
Fix available
A fix is available. Upgrade to 2024.40 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site WebSocket Hijacking in SysReptor from version 2024.28 to version 2024.30 causes attackers to escalate privileges and obtain sensitive information when a logged-in SysReptor user visits a malicious same-site subdomain in the same browser session.

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

Cross-Site WebSocket Hijacking (CSWSH) vulnerability in SysReptor allows attackers to hijack authenticated WebSocket connections when a logged-in user visits a malicious same-site subdomain. This enables privilege escalation and access to sensitive information through the hijacked WebSocket channel.

MitigationUpgrade SysReptor to version 2024.31 or later. Until patched, users should avoid browsing untrusted same-site subdomains while logged into SysReptor.

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
SysreptorApplication
Affected:>= 2024.28, < 2024.40

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 SysReptor installation version
    Check the application's version number through the web interface, API endpoint, or version file within the SysReptor installation directory. Common methods include accessing the /api/info endpoint or checking a version file in the deployment.
    Affected if The installed version is 2024.28, 2024.29, 2024.30, 2024.31, 2024.32, 2024.33, 2024.34, 2024.35, 2024.36, 2024.37, 2024.38, or 2024.39 (versions greater than or equal to 2024.28 but less than 2024.40).
  2. Confirm WebSocket endpoint exposure
    Identify if the SysReptor application exposes WebSocket endpoints (typically under /ws/ or /websocket/ paths). This can be checked by examining the application's URL routing configuration, proxy settings, or by inspecting network traffic when interacting with the application.
    Affected if WebSocket endpoints are accessible and the application uses WebSocket connections for real-time communication.
  3. Verify authentication mechanism
    Determine whether users authenticate to SysReptor and maintain active sessions. Check if the application uses session-based authentication that could be exploited through cross-site WebSocket hijacking.
    Affected if Users maintain authenticated sessions in SysReptor, as the vulnerability requires hijacking an authenticated WebSocket connection.

You are affected if your SysReptor version is 2024.28 through 2024.39 (inclusive) and users have active authenticated sessions that could be hijacked via a malicious same-site subdomain.

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 2024.40 or later
Fixed in 2024.40
Interim mitigation

Upgrade SysReptor to version 2024.31 or later. Until patched, users should avoid browsing untrusted same-site subdomains while logged into SysReptor.

Recommended fix Moderate confidence

SysReptor version 2024.40 or later

  1. 1. Back up the current SysReptor installation and database before proceeding with any changes.
  2. 2. Upgrade SysReptor to version 2024.40 or later. The specific upgrade method depends on the installation method used (e.g., Docker, pip, or other).
  3. 3. After upgrading, verify the WebSocket endpoint now implements proper origin validation or CSRF token protection.
  4. 4. Confirm the upgrade was successful by checking the SysReptor version number.
  5. 5. Clear browser sessions and require users to re-authenticate to ensure any potentially hijacked sessions are invalidated.
Caveat Review release notes for 2024.40+ to check for any breaking changes or migration requirements

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

Fix this in Sysreptor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36076 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-36076 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