Skip to content
Fencer Vulns
medium 5.3

CVE-2019-8123 json

Magento 2 Community Edition Insufficient Logging

published 2019-11-05 7 y ago modified 2026-06-17 4 mo ago also GHSA-fp5m-4mqh-849p , EUVD-2022-3814

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

An insufficient logging and monitoring vulnerability exists in Magento 1 prior to 1.9.4.3 and 1.14.4.3, Magento 2.1 prior to 2.1.19, Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3. The logging feature required for effective monitoring did not contain sufficent data to effectively track configuration changes.

Patch / fix

  • packagist magento/community-edition 2.1.19, 2.2.10, 2.3.3
  • magento magento 1.9.3.4, 1.14.4.3, 2.2.10

Exploit prediction

0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/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.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist magento/community-edition
>=2.1.0, <2.1.19
>=2.2.0, <2.2.10
>=2.3.0, <2.3.3
2.1.19
2.2.10
2.3.3

Affected products

  • Adobe Systems Incorporated Magento 1& 2

Classification

Weakness

References

Sources

Fencer Vulns 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.