Vulnerability Database · npm · lazysizes · Version

lazysizes 0.8.1

0.8.1 is affected by 2 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 5.3.2.

Critical 0 High 1 Medium 1 Low 0 Unrated 0

Released 19 Jan 2015 Licence MIT Also known from other sources 2 Newer releases 100 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

lazysizes 0.8.1 vulnerabilities

2 vulnerabilities cover lazysizes 0.8.1. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2020-7642: Cross-site scripting in lazysizes 5.4 medium 5.2.1 10 Dec 2021
Cross-Site Scripting in lazysizes N/A high 5.2.1-rc1 03 Sep 2020

Looking for another version, or everything Vulert holds for lazysizes?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About lazysizes 0.8.1

Is lazysizes 0.8.1 vulnerable?

Yes. 2 vulnerabilities in the Vulert database cover lazysizes 0.8.1: 0 critical, 1 high, 1 medium and 0 low. The upgrade Vulert recommends is 5.3.2, and each entry above names the fixed version to move to.

Which version of lazysizes should I use instead of 0.8.1?

5.3.2 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 0.8.1 the latest release of lazysizes?

No. 0.8.1 was published 19 Jan 2015, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor lazysizes for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the lazysizes version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.