How severe is CVE-2018-14020?

CVE-2018-14020 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 CVE-2018-14020?

CVE-2018-14020 affects the following packages: oxid-esales/paymorrow-module (Packagist), oxid-esales/paymorrow-module (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2018-14020?

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 CVE-2018-14020 is resolved across your whole dependency graph.

How do I detect CVE-2018-14020 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 CVE-2018-14020 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.

Is CVE-2018-14020 actively exploited in the wild?

No public exploit code has been indexed for CVE-2018-14020 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 CVE-2018-14020?

CVE-2018-14020 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th 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 CVE-2018-14020 published, and has it been updated?

CVE-2018-14020 was published on August 20, 2018 and was last updated on October 24, 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

MEDIUM severity

CVE-2018-14020 — paymorrow-module

MEDIUM

CVE-2018-14020 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 asGHSA-489x-ccjw-q7c4

Published

Aug 20, 2018

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 5, 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 CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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`

Affected Products

1 product · 3 configurations

Application

paymorrowpaymorrow

3 versions

1.0.01.0.22.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 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 CVE-2018-14020 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-14020 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works