Is klaviyo/magento2-extension 1.2 vulnerable?

Composer · 5 releases from 1.2.0 to 1.2.4 · latest klaviyo/magento2-extension is 5.2.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. klaviyo/magento2-extension 1.2.4, the last 1.2 release, is affected by 1 known security advisory (1 medium). Upgrade to 3.0.0 or later to fix all of them.

Upgrade with:composer require klaviyo/magento2-extension:^3.0.0

Is your project on an affected klaviyo/magento2-extension?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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 1.2.4

  • MediumGHSA-hvgw-gg3p-295j15 May 2024

    Read private customer data reclaiming carts in Klaviyo Magento

    Affected
    >=1.0.0 <3.0.0
    Fixed in
    3.0.0

Every klaviyo/magento2-extension 1.2.x release

Affected: 1.2.0 to 1.2.4. Latest klaviyo/magento2-extension: 5.2.0.

VersionKnown advisories
klaviyo/magento2-extension 1.2.4GHSA-hvgw-gg3p-295j
klaviyo/magento2-extension 1.2.3GHSA-hvgw-gg3p-295j
klaviyo/magento2-extension 1.2.2GHSA-hvgw-gg3p-295j
klaviyo/magento2-extension 1.2.1GHSA-hvgw-gg3p-295j
klaviyo/magento2-extension 1.2.0GHSA-hvgw-gg3p-295j

Which of your client projects are still on klaviyo/magento2-extension 1.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

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.