How severe is GHSA-489x-ccjw-q7c4?

GHSA-489x-ccjw-q7c4 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-489x-ccjw-q7c4?

GHSA-489x-ccjw-q7c4 affects the following packages: oxid-esales/paymorrow-module (Packagist), oxid-esales/paymorrow-module (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-489x-ccjw-q7c4?

Update oxid-esales/paymorrow-module to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-489x-ccjw-q7c4 is resolved across your whole dependency graph.

How do I detect GHSA-489x-ccjw-q7c4 in my Packagist dependencies?

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

How do I mitigate GHSA-489x-ccjw-q7c4 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-489x-ccjw-q7c4?

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

Is GHSA-489x-ccjw-q7c4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-489x-ccjw-q7c4 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.

What is the EPSS score for GHSA-489x-ccjw-q7c4?

GHSA-489x-ccjw-q7c4 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 64th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-489x-ccjw-q7c4 published, and has it been updated?

GHSA-489x-ccjw-q7c4 was published on May 13, 2022 and was last updated on December 5, 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

MEDIUM severity

GHSA-489x-ccjw-q7c4 — oxid-esales/paymorrow-mod…

MEDIUM

GHSA-489x-ccjw-q7c4 is a medium-severity (CVSS 5.3) vulnerability in oxid-esales/paymorrow-module. A fix is available for oxid-esales/paymorrow-module — see the affected versions and patch details below.

Paymorrow Improper Input Validation vulnerability

Also known asCVE-2018-14020

Published

May 13, 2022

Updated

Dec 5, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-489x-ccjw-q7c4 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs affected

🐘oxid-esales/paymorrow-module🐘oxid-esales/paymorrow-module

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

An issue was discovered in the Paymorrow module 1.0.0 before 1.0.2 and 2.0.0 before 2.0.1 for OXID eShop. An attacker can bypass delivery-address change detection if the payment module doesn't use eShop's checkout procedure properly. To do so, the attacker must change the delivery address to one that is not verified by the Paymorrow module.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`oxid-esales/paymorrow-module`	≥ 1.0.0&&< 1.0.2	1.0.2`composer require oxid-esales/paymorrow-module:^1.0.2`
🐘Packagist	`oxid-esales/paymorrow-module`	≥ 2.0.0&&< 2.0.1	2.0.1`composer require oxid-esales/paymorrow-module:^2.0.1`

Detection & mitigation playbook

Open-source dependency

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

Tailored to GHSA-489x-ccjw-q7c4. 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-489x-ccjw-q7c4 in your dependencies?

O3 Security finds GHSA-489x-ccjw-q7c4 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