Threat Intelligence Database
Comprehensive database of the latest cyber threats affecting organizations worldwide. Filter and search to find specific threat intelligence relevant to your organization.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threat Intelligence
Click on any threat for detailed analysis and mitigation recommendations
0 Vendure through 3.7.1, fixed in commit f67ef5f, contains a cross-channel authorization bypass vulnerability in stock-location.service.ts and asset.service.ts update methods that allows channel-scoped administrators to modify other tenants' data. Attackers can supply global IDs of StockLocation or Asset entities from different channels to overwrite inventory locations or catalog assets belonging to other tenants without proper channel isolation validation. Join the discussion | CVE Database V5 | 07/30/2026, 14:40:02 UTC Added: 07/30/2026, 16:52:59 UTC |
0 Vendure versions prior to 2.3.4, 3.5.7, and 3.6.2 contain an unauthenticated SQL injection vulnerability in the Shop API due to unsafe interpolation of a user-controlled query string parameter. This allows attackers to execute arbitrary SQL commands on the database. The Admin API is also vulnerable but requires authentication for exploitation. Vendure has released patched versions that fix this by parameterizing queries and providing a hotfix that validates the languageCode input to block injection attempts. Join the discussion | CVE Database V5 | 04/21/2026, 19:24:59 UTC Added: 04/21/2026, 19:31:23 UTC |
0 Vendure is an open-source headless commerce platform. Prior to version 3.5.3, the `NativeAuthenticationStrategy.authenticate()` method is vulnerable to a timing attack that allows attackers to enumerate valid usernames (email addresses). In `packages/core/src/config/auth/native-authentication-strategy.ts`, the authenticate method returns immediately if a user is not found. The significant timing difference (~200-400ms for bcrypt vs ~1-5ms for DB miss) allows attackers to reliably distinguish between existing and non-existing accounts. Version 3.5.3 fixes the issue. Join the discussion | CVE Database V5 | 01/30/2026, 15:11:40 UTC Added: 01/30/2026, 15:27:48 UTC |
Showing 1 to 3 of 3 results