dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-48740

MEDIUM · 5.9 CVSS v4.0 Published 2025-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
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
A Cross-Site Request Forgery (CSRF) vulnerability in StrangeBee TheHive 5.2.0 before 5.2.16, 5.3.0 before 5.3.11, 5.4.0 before 5.4.10, and 5.5.0 before 5.5.1 allows a remote attacker to trigger requests on their victim's behalf, if the attacker lures a privileged user, authenticated with basic authentication.

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

A CSRF vulnerability in StrangeBee TheHive allows remote attackers to trick privileged users authenticated via basic authentication into performing unintended actions on the application. The vulnerability affects versions 5.2.0-5.2.15, 5.3.0-5.3.10, 5.4.0-5.4.9, and 5.5.0, allowing cross-site request forgery attacks against authenticated users.

MitigationUpgrade to TheHive version 5.2.16, 5.3.11, 5.4.10, or 5.5.1 or later. Additionally, implement anti-CSRF tokens and validate Origin/Referer headers on state-changing operations as defense-in-depth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 TheHive installation
    Locate TheHive by checking for the web service running on common ports (9000, 9001) or look for 'thehive' processes. Check /opt/thehive or similar installation directories, or query your container/orchestration system if running in containers.
    Affected if TheHive application is found on the system
  2. Determine installed TheHive version
    Log into TheHive admin interface and navigate to Administration > System > Information to view the version. Alternatively, check the thehive.conf configuration file or the build info via API endpoint /api/status.
    Affected if Version is 5.2.0-5.2.15, 5.3.0-5.3.10, 5.4.0-5.4.9, or 5.5.0
  3. Check if basic authentication is enabled
    Review the authentication configuration in thehive.conf (or application.conf) under the 'auth' section. Look for 'provider = basic' or similar basic authentication settings. In the admin UI, check Authentication providers in the configuration.
    Affected if Basic authentication provider is configured and enabled
  4. Verify network accessibility of TheHive interface
    Confirm the TheHive web interface is reachable from network locations where untrusted parties could initiate requests. Check firewall rules, reverse proxy configuration, and bind addresses in thehive.conf (http.address or play.http.address).
    Affected if TheHive is accessible from network segments beyond the trusted admin workstation network

The environment is affected if TheHive version falls within 5.2.0-5.2.15, 5.3.0-5.3.10, 5.4.0-5.4.9, or 5.5.0 AND basic authentication is enabled AND the web interface is network-accessible to potential attackers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to TheHive version 5.2.16, 5.3.11, 5.4.10, or 5.5.1 or later. Additionally, implement anti-CSRF tokens and validate Origin/Referer headers on state-changing operations as defense-in-depth.

Recommended fix Moderate confidence

Upgrade to TheHive 5.2.16 (if on 5.2.x), 5.3.11 (if on 5.3.x), 5.4.10 (if on 5.4.x), or 5.5.1 (if on 5.5.0)

  1. 1. Identify the current TheHive version by checking the application's about page or running `thehive --version`
  2. 2. Based on the current version, determine the minimum target version: for 5.2.x go to 5.2.16, for 5.3.x go to 5.3.11, for 5.4.x go to 5.4.10, for 5.5.0 go to 5.5.1
  3. 3. Back up the existing TheHive configuration, database, and any custom integrations
  4. 4. Download the appropriate fixed version from the official StrangeBee GitHub repository or TheHive download page
  5. 5. Follow the standard TheHive upgrade documentation for your deployment method (RPM, DEB, Docker, or manual installation)
  6. 6. After upgrade, verify the application starts successfully and all services are running
  7. 7. Test that authenticated users can perform operations normally
  8. 8. Review TheHive logs for any errors during startup and operation
Caveat Review TheHive release notes for any breaking changes between your current version and the target version before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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