Is klaviyo/magento2-extension 2.2 vulnerable?
Composer · 1 release from 2.2.0 to 2.2.0 · latest klaviyo/magento2-extension is 5.2.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. klaviyo/magento2-extension 2.2.0, the last 2.2 release, is affected by 1 known security advisory (1 medium). Upgrade to 3.0.0 or later to fix all of them.
composer require klaviyo/magento2-extension:^3.0.0Is your project on an affected klaviyo/magento2-extension?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting klaviyo/magento2-extension 2.2.0
Read private customer data reclaiming carts in Klaviyo Magento
- Affected
- >=1.0.0 <3.0.0
- Fixed in
- 3.0.0
Which of your client projects are still on klaviyo/magento2-extension 2.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact klaviyo/magento2-extension version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other klaviyo/magento2-extension versions
- klaviyo/magento2-extension 4.1
- klaviyo/magento2-extension 4.0
- klaviyo/magento2-extension 3.0
- klaviyo/magento2-extension 2.1
- klaviyo/magento2-extension 2.0
- klaviyo/magento2-extension 1.2
- klaviyo/magento2-extension 5.2
- klaviyo/magento2-extension 5.1
- klaviyo/magento2-extension 5.0
- klaviyo/magento2-extension 4.4
- klaviyo/magento2-extension 4.3
- klaviyo/magento2-extension 4.2
- All klaviyo/magento2-extension advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.