Paymorrow Improper Input Validation vulnerability

published 2018-08-20 8y ago modified 2026-06-17 4mo ago also GHSA-489x-ccjw-q7c4 , EUVD-2022-2337

cvss: 5.3; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

packagist oxid-esales/paymorrow-module 1.0.2, 2.0.1

Is CVE-2018-14020 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.08% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.3	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub	3.0	5.3	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	oxid-esales/paymorrow-module	>=1.0.0, <1.0.2 >=2.0.0, <2.0.1	1.0.2 2.0.1

References

bugs.oxid-esales.com /view.php?id=6801
web, vendor-advisory
oxidforge.org /en/security-bulletin-2018-003.html
web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2018-14020
advisory
github.com /OXID-eSales/paymorrow-module
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.