How severe is GHSA-hvgw-gg3p-295j?

No CVSS score has been assigned to GHSA-hvgw-gg3p-295j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hvgw-gg3p-295j?

GHSA-hvgw-gg3p-295j affects the following packages: klaviyo/magento2-extension (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-hvgw-gg3p-295j?

Update klaviyo/magento2-extension to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hvgw-gg3p-295j is resolved across your whole dependency graph.

How do I detect GHSA-hvgw-gg3p-295j in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for klaviyo/magento2-extension, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hvgw-gg3p-295j if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hvgw-gg3p-295j?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hvgw-gg3p-295j can be triaged on real exposure rather than presence alone.

Is GHSA-hvgw-gg3p-295j actively exploited in the wild?

No public exploit code has been indexed for GHSA-hvgw-gg3p-295j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-hvgw-gg3p-295j published, and has it been updated?

GHSA-hvgw-gg3p-295j was published on May 15, 2024 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-hvgw-gg3p-295j — klaviyo/magento2-extension

Fix: klaviyo/magento2-klaviyo#107

GHSA-hvgw-gg3p-295j is a security vulnerability in klaviyo/magento2-extension. A fix is available for klaviyo/magento2-extension — see the affected versions and patch details below.

Read private customer data reclaiming carts in Klaviyo Magento

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘klaviyo/magento2-extension

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

A researcher identified an endpoint in a thirth party module Klaviyo Magento 2 which allows to read private customer data from stores. It works by reclaiming any guest-cart as your own and reading the private data for the orders in the Magento API.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`klaviyo/magento2-extension`	≥ 1.0.0&&< 3.0.0	3.0.0`composer require klaviyo/magento2-extension:^3.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for klaviyo/magento2-extension, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update klaviyo/magento2-extension to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hvgw-gg3p-295j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hvgw-gg3p-295j can be triaged on real exposure rather than presence alone.

Tailored to GHSA-hvgw-gg3p-295j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-hvgw-gg3p-295j in your dependencies?

O3 Security finds GHSA-hvgw-gg3p-295j across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works