Skip to main content

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

CVE-2024-45389

Severity Medium
Score 5.4/10

Summary

Pagefind is a fully static search library, initializes its dynamic JavaScript and WebAssembly files relative to the location of the first script the user loads. This information is gathered by looking up the value of "document.currentScript.src". In @pagefind/modular-ui, and @pagefind/default-ui packages versions prior to 1.1.1, it is possible to "clobber" this lookup with otherwise benign HTML on the page. This will cause "document.currentScript.src" to resolve as an external domain, which will then be used by Pagefind to load dependencies. This exploit would only work in the case that an attacker could inject HTML to a live, hosted, website. In these cases, this would act as a way to escalate the privilege available to an attacker. This assumes they have the ability to add some elements to the page (for example, "img" tags with a "name" attribute), but not others, as adding a "script" to the page would itself be the Cross-site Scripting vector. Pagefind has tightened this resolution, by ensuring the source is loaded from a valid script element. There are no reports of this being exploited in the wild via Pagefind.

  • LOW
  • NETWORK
  • LOW
  • CHANGED
  • REQUIRED
  • LOW
  • LOW
  • NONE

CWE-79 - Cross Site Scripting

Cross-Site Scripting, commonly referred to as XSS, is the most dominant class of vulnerabilities. It allows an attacker to inject malicious code into a pregnable web application and victimize its users. The exploitation of such a weakness can cause severe issues such as account takeover, and sensitive data exfiltration. Because of the prevalence of XSS vulnerabilities and their high rate of exploitation, it has remained in the OWASP top 10 vulnerabilities for years.

Advisory Timeline

  • Published