Skip to content
Fencer Intel
medium 4.9

CVE-2019-8124 json

Magento 2 Community Edition Insufficient Logging

published 7y ago modified 4mo ago also GHSA-x5q5-6wvf-2fpq , EUVD-2022-5720

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

Summary

An insufficient logging and monitoring vulnerability exists in Magento 2.1 prior to 2.1.19, Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3. Failure to track admin actions related to design configuration could lead to repudiation attacks.

Patch / fix

  • packagist magento/community-edition 2.1.19, 2.2.10, 2.3.3
  • magento magento 2.1.19, 2.2.10, 2.3.2

Is CVE-2019-8124 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

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

CVSS scores

assigned by version score vector
NVD 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:P/A:N
GitHub 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/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 2

Classification

Weakness
  • CWE-345 Insufficient Verification of Data Authenticity

References

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.