Practical Security Guides For Your Team

Your website uses a popular library called DOMPurify to clean up user-submitted content before displaying it — think of it like a filter that strips out dangerous code. A flaw in the version you're running means that filter has a gap: under specific conditions, a crafted piece of content can slip through and run malicious code in a visitor's browser. A patch is already available and the fix is a straightforward version upgrade.

Your application uses a library called DOMPurify to clean up untrusted content (like user-submitted text) before displaying it on your website. A flaw in the version you're running means that cleaning process can be bypassed under specific conditions, potentially allowing malicious scripts to run in a visitor's browser. Upgrading to the latest version closes the gap.

Your website uses an outdated version of React (a popular tool for building web pages) that has a known security flaw. If your site generates pages on the server and allows user input to influence how those pages are built, an attacker could inject malicious code that runs in your visitors' browsers. This only affects server-rendered React apps — if your site is purely client-side, you are not at risk.

Your website uses an old version of jQuery (a common JavaScript tool) that has a known security flaw. If your site processes any HTML content from users or external sources, that content could contain hidden instructions that run automatically — without any warning. Upgrading jQuery to a modern version closes this gap.

Your website uses AngularJS 1.x, an old JavaScript framework that was officially retired in early 2022 and will never receive security updates again. A known flaw in this version can allow malicious scripts to run in a visitor's browser under specific conditions. Because the framework is no longer maintained, this particular vulnerability has no official patch — the real fix is to plan a migration to a modern framework.

Your website has a security header called a Content Security Policy (CSP) — think of it like a bouncer that controls which scripts are allowed to run on your pages. Right now, two settings in that policy ('unsafe-inline' and 'unsafe-eval') are telling the bouncer to let almost anyone in, which largely defeats the purpose of having one. This is a defence layer that isn't doing its job properly, not an active attack.

Your website uses an outdated version of Bootstrap — a popular design toolkit used by millions of websites. The version in use has a known flaw in its collapsible panel feature that could allow someone to inject malicious code into your pages if they can influence the content on your site. This is a medium-priority issue: it requires specific conditions to exploit, but it is a well-documented vulnerability with a straightforward fix.

Your website uses an outdated version of jQuery, a common JavaScript tool. This version has a known flaw: if your site makes background data requests to other websites, a compromised or malicious third-party server could send back code that runs automatically in your visitors' browsers. Think of it like ordering a package and having the delivery driver hand you something unexpected that activates the moment you open the door.

Your web server is missing a simple one-line instruction that tells browsers how to handle the files it sends. Without it, some browsers may try to 'guess' what type of file they've received — and in certain situations, that guess could cause a harmless-looking file to be treated as executable code. Think of it like a label on a package: without it, the delivery driver has to guess what's inside.

Your website uses an outdated version of Bootstrap — a popular design toolkit — that has a known security flaw. A malicious actor who can influence tooltip or popover content on your site could use this flaw to run unwanted code in a visitor's browser. The fix is a straightforward library upgrade.

Your website uses an old version of Bootstrap (a popular design toolkit) that has a known security flaw. A specific button feature in this version doesn't properly filter out malicious code, meaning that if any user-supplied text ever reaches those buttons, it could run unwanted scripts in your visitors' browsers. Bootstrap 3 is also no longer maintained, so no official fix will be released for this version.

Your website uses an outdated version of Bootstrap (a popular design toolkit) that contains a known security flaw. An attacker who can influence the content on your pages could use this flaw to run malicious code in your visitors' browsers. The fix is straightforward: update Bootstrap to a newer version.