Show your clients what is being exploited right now
A free widget for MSPs, IT providers and security teams: a live list of vulnerabilities confirmed as exploited in the wild, on your website, intranet or client portal. Updated hourly. No account, no cookies, no tracking.
Build your embed code
1. How to embed
Runs in its own sandbox on our domain. Nothing of ours runs on your page.
<iframe src="https://strikecyber.com/radar/widget/frame/5-light/" title="Vulnerabilities being exploited now" width="100%" height="394" style="max-width:520px;border:0" loading="lazy" referrerpolicy="no-referrer" sandbox="allow-popups allow-popups-to-escape-sandbox"></iframe>
Live preview
Updated hourlyThe preview sits on a light background so you can see how it will look on your site. Keep the small credit link in place.
How it works
- 1CISA adds a vulnerability to its Known Exploited Vulnerabilities catalogue once there is evidence attackers are using it.
- 2Our hourly job saves it to our own copy of the data, with the vendor, product, date and whether ransomware groups use it.
- 3The widget is rebuilt from that copy every hour and served from a global cache, so it loads fast and costs your site nothing.
- 4Each entry links to its Threat Radar page, with how to check whether you are affected and what to do, in plain English.
What your visitors see
- The product. Vendor and product name, such as Fortinet FortiOS, linked to the full write-up.
- The CVE. The official identifier, so IT teams can search their own systems.
- When it was added. The date CISA confirmed exploitation.
- Ransomware. A red flag when ransomware groups are known to use it.
Security: what embedding does and does not open up
We are a penetration testing firm, so we tested this the way we would test a client's.
- Runs our code on your page
- Iframe: No. It is a separate page in a sandbox.
- Script: Yes, like any third-party script.
- Can read your page, cookies or forms
- Iframe: No. The browser blocks it.
- Script: It does not, but a script could.
- JavaScript inside the widget
- Iframe: None. Our policy blocks all scripts.
- Script: One small script, text only.
- Network requests after loading
- Iframe: None.
- Script: None. The data is built in.
- Cookies or tracking
- Iframe: None.
- Script: None.
- Fits your page width
- Iframe: Yes, up to 520px. Set the height once.
- Script: Yes, sizes itself.
- Works with a strict Content Security Policy
- Iframe: Add our domain to frame-src.
- Script: Add our domain to script-src.
The widget never does these
- Collect anything about your visitors. No cookies, no fingerprinting, no analytics inside the widget.
- Load other people's code. No ads, no trackers, no third-party scripts or fonts.
- Use HTML from the data. Vendor and product names are written as plain text, so a malicious entry cannot inject code.
- Accept options from the address bar. The iframe exists in 20 fixed versions, so it cannot be used to show anything else.
The honest trade-off with the script
Any script you embed runs with your page's full permissions. Ours is small, writes plain text only and reads nothing from your page, but you are still trusting our website to stay secure. If it were ever compromised, a changed script would run on your page too.
Browsers offer a lock for this (subresource integrity), but it only works for files that never change, and this list changes every hour.
That is why the iframe is our recommendation, and the only option we would suggest for banking, health, government or login pages. It keeps the same live data with none of that risk.
Options
- Items
- 1 to 10 (default 5)
- How many of the most recent exploited vulnerabilities to show. Iframe: the number in the address, such as 5-light. Script: data-count.
- Theme
- light or dark
- Match your page background. Iframe: light or dark in the address. Script: data-theme="dark".
- Placement (script only)
- an element id
- data-target renders into that element instead of where the script tag sits.
- Height (iframe only)
- pixels
- The builder sets this for you. Increase it if your page uses a larger base font.
Prefer the raw data?
Common questions
Is the widget free?
Yes. There is no account, no sign-up and no limit. We only ask that you keep the small credit link to the Threat Radar.
Which embed should I use?
Use the iframe. It runs in its own sandbox on our domain, so nothing we serve can touch your page, your visitors' sessions or your forms. Use the script only if you need the list to sit in your page's own layout and you are comfortable running a third-party script.
Where does the data come from?
The CISA Known Exploited Vulnerabilities catalogue, the same list the US and Australian governments use to prioritise patching. An entry appears only once there is evidence of exploitation in the wild.
How often does it update?
Every hour. Your page does not need to change; the next visitor sees the new list.
Does it slow my site down?
No. The iframe loads lazily and the script loads asynchronously, and both are served from a global cache. Neither makes further requests once loaded.
What do you learn about my visitors?
Nothing beyond what any web request carries: our host keeps standard request logs (IP address and browser) for security. The embed codes tell browsers not to send your page address, and the widget sets no cookies.
Can it be used on a client portal or intranet?
Yes. It needs no login and reads nothing from the page, so it is safe on internal pages too. Many MSPs add it to their client portal as a weekly talking point.
Not sure which of these you expose?
A free Cyber Security Snapshot maps your internet-facing systems, so you know which exploited vulnerabilities apply to you.