How severe is GHSA-mqq7-wxx5-mp8h?

No CVSS score has been assigned to GHSA-mqq7-wxx5-mp8h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mqq7-wxx5-mp8h?

GHSA-mqq7-wxx5-mp8h affects the following packages: prestashop/ps_checkout (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-mqq7-wxx5-mp8h?

Update prestashop/ps_checkout to 5.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mqq7-wxx5-mp8h is resolved across your whole dependency graph.

How do I detect GHSA-mqq7-wxx5-mp8h in my Packagist dependencies?

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

How do I mitigate GHSA-mqq7-wxx5-mp8h 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-mqq7-wxx5-mp8h?

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

Is GHSA-mqq7-wxx5-mp8h actively exploited in the wild?

No public exploit code has been indexed for GHSA-mqq7-wxx5-mp8h 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-mqq7-wxx5-mp8h published, and has it been updated?

GHSA-mqq7-wxx5-mp8h was published on April 30, 2026 and was last updated on September 10, 2026. 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-mqq7-wxx5-mp8h — prestashop/ps_checkout

GHSA-mqq7-wxx5-mp8h is a security vulnerability in prestashop/ps_checkout. A fix is available for prestashop/ps_checkout — see the affected versions and patch details below.

ps_checkout allows unauthorized method invocation through unvalidated parameter

Published

Apr 30, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘prestashop/ps_checkout

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

Impact

Unvalidated parameter can lead to some unauthorized method invocation with very little possibilities.

Patches

The problem has been patched in versions

v5.3.0 for PrestaShop 1.7 (build number: 7.5.3.0)
v5.3.0 for PrestaShop 8 (build number: 8.5.3.0)
v5.3.0 for PrestaShop 9 (build number: 9.5.3.0)

Read the Versioning policy to learn more about the build numbers.

Credits

PrestaShop thanks PATICEO for reporting the issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`prestashop/ps_checkout`	all versions	5.3.0`composer require prestashop/ps_checkout:^5.3.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for prestashop/ps_checkout, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update prestashop/ps_checkout to 5.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mqq7-wxx5-mp8h 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-mqq7-wxx5-mp8h can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mqq7-wxx5-mp8h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Unvalidated parameter can lead to some unauthorized method invocation with very little possibilities. ### Patches The problem has been patched in versions - v5.3.0 for PrestaShop 1.7 (build number: 7.5.3.0) - v5.3.0 for PrestaShop 8 (build number: 8.5.3.0) - v5.3.0 for PrestaShop 9 (build number: 9.5.3.0) Read the [Versioning policy](https://github.com/PrestaShopCorp/ps_checkout/wiki/Versioning) to learn more about the build numbers. ### Credits PrestaShop thanks [PATICEO](https://www.paticeo.com/) for reporting the issue.

O3 Security · Impact-Aware SCA

Is GHSA-mqq7-wxx5-mp8h in your dependencies?

O3 Security finds GHSA-mqq7-wxx5-mp8h 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