CVE-2025-48741
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 · uneditedA Broken Access Control vulnerability in StrangeBee TheHive 5.2.0 before 5.2.16, 5.3.0 before 5.3.11, and 5.4.0 before 5.4.10 allows remote, authenticated, and unprivileged users to retrieve alerts, cases, logs, observables, or tasks, regardless of the user's permissions, through a specific API endpoint.
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 confidenceBroken Access Control in StrangeBee TheHive allows authenticated but unprivileged users to bypass permission checks through a specific API endpoint, enabling unauthorized access to alerts, cases, logs, observables, and tasks regardless of assigned user permissions.
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
- Low
- Authentication
- X
- User interaction
- A
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify TheHive installation and versionCheck the running service version. On Linux, look in /etc/thehive/application.conf for 'app.version' or check the service startup logs. Alternatively, query the API at GET /api/status if the service is running.Affected if The installed version is below 5.2.16, below 5.3.11, or below 5.4.10 (any version before 5.4.10 is likely affected)
-
Verify the vulnerable API endpoint is accessibleAttempt an authenticated request to a protected endpoint using an unprivileged user account. For example, try to access GET /api/alert (or /api/case) with a standard user who should not have access to certain alerts or cases. Check if the request returns data that should be restricted based on the user's role.Affected if An authenticated but unprivileged user can access alerts, cases, logs, observables, or tasks that they should not have permission to view
-
Review user role assignmentsCheck the user database or TheHive admin panel for users with standard or basic roles. TheHive typically has roles like admin, analyst, and read-only. Identify accounts that are not admin but have authenticated access.Affected if There are authenticated non-admin users present in the system who could potentially exploit this bypass
-
Inspect audit logs for unauthorized access patternsReview TheHive audit logs (typically found in /var/log/thehive/audit or via the UI) for cases where standard users accessed data outside their permission scope. Look for access to objects they were not assigned to.Affected if Audit logs show standard users accessing data across cases, alerts, or tasks they were not explicitly granted access to
A user is affected if TheHive version is below 5.4.10 (or below 5.3.11/5.2.16) AND there are non-admin authenticated users who can access the API endpoint in question.
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 · scopedUpgrade TheHive to version 5.2.16, 5.3.11, or 5.4.10 or later to apply the access control fix that properly enforces user permissions on the vulnerable API endpoint.
TheHive 5.2.16 (for 5.2.x), 5.3.11 (for 5.3.x), or 5.4.10 (for 5.4.x) - upgrade to the appropriate fixed version based on current branch
- Identify the currently installed TheHive version using the administration console or CLI
- Determine which version branch is currently in use (5.2.x, 5.3.x, or 5.4.x)
- For version 5.2.x: Upgrade to version 5.2.16 or later
- For version 5.3.x: Upgrade to version 5.3.11 or later
- For version 5.4.x: Upgrade to version 5.4.10 or later
- Follow the standard TheHive upgrade documentation for your deployment method (Docker, RPM/DEB package, or manual installation)
- After upgrade, verify that the access control vulnerability is resolved by testing that unprivileged users can no longer access resources outside their assigned permissions
- Consult the TheHive 5.2.16, 5.3.11, or 5.4.10 release notes for any additional migration steps
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48741 — 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-48741 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