CVE-2024-22877
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 · uneditedStrangeBee TheHive 5.2.0 to 5.2.8 is vulnerable to Cross Site Scripting (XSS) in the case reporting functionality. This feature allows an attacker to insert malicious JavaScript code inside the template or its variables, that will be executed in the context of the TheHive application when the HTML report is opened.
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 confidenceTheHive 5.2.0 to 5.2.8 contains a stored Cross-Site Scripting (XSS) vulnerability in the case reporting functionality. Attackers can inject malicious JavaScript code into report templates or their variables, which executes when users open the generated HTML report in the application context.
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>= 5.2.0, <= 5.2.8CVSS 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.
-
Verify TheHive versionCheck the installed TheHive version by accessing the application admin interface, checking the built-in /api/version endpoint, or reviewing system package information (e.g., dpkg, rpm, or Docker image tag)Affected if The installed version is 5.2.0, 5.2.1, 5.2.2, 5.2.3, 5.2.4, 5.2.5, 5.2.6, 5.2.7, or 5.2.8
-
Confirm case reporting is in useNavigate to TheHive case management interface and verify that the report generation feature has been used or templates exist. Check for any custom report templates in the configuration or database.Affected if Case reports have been generated or custom report templates exist in the system
-
Inspect report templates for injected scriptsAccess the report template configuration (typically found in the admin settings under Report Templates or Case Templates) and examine the template content and variable values for suspicious JavaScript tags, event handlers, or encoded payloadsAffected if Any report template contains unescaped HTML, script tags, or JavaScript event handlers in template fields or variable values
-
Review recent case reports for malicious contentExamine recent HTML reports generated through TheHive by opening them in the application and inspecting the page source, or check the underlying report data in the database for patterns like <script, javascript:, onerror, onload, or other XSS vectorsAffected if Any generated HTML reports contain unsanitized user-supplied content that could execute JavaScript
You are affected if TheHive version 5.2.0 through 5.2.8 is running AND the case reporting feature has been used with templates containing unsanitized input that could execute malicious scripts when reports are viewed.
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.
From vendor dataUpgrade to TheHive version 5.2.9 or later which contains the security patch. Alternatively, implement strict input validation and output encoding on the template rendering engine to neutralize malicious script payloads.
- 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-22877 — 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-22877 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