The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsUpgrade astro to version 7.4.5 or higher.
astro is an Astro is a modern site builder with web best practices, performance, and DX front-of-mind.
Affected versions of this package are vulnerable to Incomplete List of Disallowed Inputs via insufficient sanitization of dynamic tag names in the sanitizeElementName helper and the JSX renderer. When a dynamic tag resolves to a string, Astro renders it as a raw HTML element name. The existing filter removed characters such as &, <, >, quotes, and whitespace, but did not handle /. Because HTML parsers treat / inside a tag as an attribute separator, a tag name such as img/src/onerror=alert(1) is rendered as an <img> element with an injected onerror attribute. The JSX renderer used for MDX did not apply any filter to string tag names at all, making it fully unguarded. An attacker who can control the value passed as a dynamic tag name - for example through a URL query parameter - can inject arbitrary HTML attributes and execute JavaScript in the victim's browser.
Note: This is only exploitable in applications that use untrusted input (such as a request parameter or an uncontrolled CMS field) as all or part of an element name, as Astro itself never derives element names from request data.
Before upgrading, do not use untrusted input as an element name. If dynamic element selection is required, map the untrusted input to a fixed set of known, safe tag names.