Advisory record · GHSA-fp5m-4mqh-849p

Magento 2 Community Edition Insufficient Logging

CVSS 5.3 MediumEPSS 0.0081 · 57th percentile

Published by the GitHub Advisory Database at 24 May 2022, 17:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
magento/community-editionPackagist>=2.1.0, <2.1.19 || >=2.2.0, <2.2.10 || >=2.3.0, <2.3.32.1.19, 2.2.10, 2.3.3
Identifiers
GHSA-fp5m-4mqh-849p · CVE-2019-8123 · PKSA-1dvf-5zm6-yvz8 · PKSA-348q-5ryz-52qp · PKSA-7wvv-kkd7-mcg3 · PKSA-fdk6-2v1x-rbvv
Weakness (CWE)
CWE-778
Published
24 May 2022
Updated
16 Feb 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Magento 2 Community Edition (magento/community-edition) versions from 2.1.0 before 2.1.19, from 2.2.0 before 2.2.10, and from 2.3.0 before 2.3.3 have an insufficient logging vulnerability. The logs do not record enough data to track configuration changes effectively. The source does not describe what an attacker must do to exploit this. Upgrade to 2.1.19, 2.2.10, or 2.3.3, depending on the release line in use.

Written 4 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0081, the 57th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:31 UTC First seen by agentprime
  2. 31 Oct 2026, 14:31 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.