Trust profileHow to read thisFive separate questions a buyer actually asks, each answered with its own evidence and a link to the source. There is deliberately no overall score: a single number invites comparison it cannot support, and would mostly reflect how much of StrangeBee we have managed to scan rather than anything about the vendor.
Not checked means we have not looked yet, and is never counted against a vendor. Limited means we did look, but found only one line of evidence — enough to report, not enough to corroborate.
checked 12 of 16 signals
Limited
Independently verified
Has anyone other than the vendor confirmed this?
checked 3 of 4
Nothing here has been confirmed by an independent third party yet.
No third-party certifications found
Profile not claimed by the vendor
Limited
Operating durability
Is this a real, durable business?
checked 3 of 4
How long this vendor has been operating, and who stands behind them.
Domain registered 2018 — 8 years ago
Headquarters location not disclosed on their site
Mixed
Behaviour under stress
What do they do when something goes wrong?
checked 2 of 3
What their public record shows about handling vulnerabilities and outages.
7 published CVE(s) — a public disclosure record exists
1 rated critical
No public status page found
Limited
Disclosure posture
Do they tell you the awkward things unprompted?
checked 2 of 3
How much this vendor volunteers before you have to ask.
No trust center found
Data coverage: 13/100What this measures (and doesn't)
Not a quality rating or endorsement — a measure of how much verified, disclosed data we actually have about this vendor. A low score usually means "we don't have much verified information yet," not "this is a bad vendor." Never used to sort or rank vendor lists.
The platform admin controls the formula's weights.
Data coverage profileHow to read thisThe same four components behind the data coverage score above, shaped instead of listed — a vendor strong on verification but thin on buyer feedback looks visibly different from one that's the other way around. Security and feedback plot at the neutral midpoint (50) when there's no data yet (no products tracked, no reviews), matching how the actual score itself treats missing data — not a guess either way.
Buyer reviewsUI-14 — verified-buyer reviewsWritten only by domain-verified buyers at other companies, attributed to their company domain (never their identity), and moderated. Buyer-sourced opinion, clearly separate from the neutral catalog facts above — and never an input to search or comparison ordering.
verified buyers only
No buyer reviews yet.
Reputation ratingUI-20 — anonymous ratingA single anonymous 5-star signal from buyers, resellers, and analysts who've engaged with this vendor — separate from the domain-attributed reviews above. No rater identity is ever shown, not even at company level.
anonymous
No ratings in this window yet.
Security case management platform for SOCs, CERTs, and CSIRTs AI-generated from public sourcesThe starting point for every profile: auto-generated by 0-Doubt from public vendor materials, and not yet confirmed by the vendor or an independent analyst. Nothing here is hidden or overstated — it simply has not been reviewed yet.Where every profile starts, before the vendor or an analyst has reviewed it. A higher label means a more independent source — not a better product.How trust works →
Security & trust signalsAbout these signalsCertifications are labeled by how well evidenced each one is — confirmed in a public registry, stated by the vendor, or merely detected on a page — and every claim links to its source. Security headers are checked live against the vendor's homepage, re-checked every 90 days. These are independent signals and are not blended into a single score.
9 of 9 technical checks completed — not a score, just coverage
Recent news (4)Where this comes fromCollected automatically from StrangeBee's own public feeds — a GitHub release feed, changelog, status page or company blog. Each headline links to the original source. Nothing here is written or reviewed by 0-Doubt, and this list is not a complete record of what the vendor has shipped: it only covers what they publish in a machine-readable feed.
CVE severity over timeUI-24 — CVE severity timelineEvery known CVE with a disclosure date and severity, plotted by when it was published — lets you see whether disclosures are trending toward more or less severe, not just a raw count. Same NVD-sourced, name-matched data as the list below.
Known CVEs (7)About this listSourced from the public NVD database, matched by vendor name. This is a name-based match, not exact version tracking — always check the linked NVD record for affected versions before drawing conclusions. “New” means published within the last 30 days. “Actively exploited” means CISA's Known Exploited Vulnerabilities (KEV) catalog confirms real-world exploitation, not just a theoretical severity score.
A 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, c…
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 reques…
A Server-Side Request Forgery (SSRF) 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 remote authenticated attackers wit…
Product information on this page is auto-generated by 0-Doubt from public sources and not yet confirmed by the vendor or an independent analyst, unless an item is individually labelled otherwise. How trust works →
Collaborative case management platform for incident response and investigation
No bug bounty or vulnerability disclosure policy found
Limited
Momentum
Are they still shipping, or coasting?
checked 2 of 2
Whether this vendor is visibly still building.
5 public announcement(s) in the last 180 days — most recently 2026-07-15
CVE-2025-48738
2025
An e-mail flooding 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 unauthenticated remote attackers to use the password…
StrangeBee 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 templa…
StrangeBee TheHive 5.1.0 to 5.1.9 and 5.2.0 to 5.2.8 is vulnerable to Cross Site Scripting (XSS) in the case attachment functionality which enables an attacker to upload a malicious HTML file with Jav…
An issue in StrangeBee TheHive v.5.0.8, v.4.1.21 and Cortex v.3.1.6 allows a remote attacker to gain privileges via Active Directory authentication mechanism.
