Skip to main content
CVE-2026-128047VulnerabilityPublished

OpenMage magento-lts before 20.18.2 and 21.0.0-beta pre-releases before 21.0.0-beta3 generate customer

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-128047· Critical 9.2

Not known to be exploited · CVSS 9.2 Critical : upgrade to 20.18.2 as a priority.

Data as of 13 Nov 2026, 13:38 UTC

CVSS 4.0 base score
9.2Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.09.2
CNA (VulnCheck)CVSS 3.18.1
Patch
Available – fixed in 20.18.2, 21.0.0-beta3
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade magento-lts to 20.18.2; magento-lts to 21.0.0-beta3; openmage/magento-lts to 21.0.0-beta3 or 20.18.2.

Affected software

ProductAffectedFixed in
OpenMagemagento-ltsAffected
  • <20.18.2
Fixed in
  • 20.18.2
OpenMagemagento-ltsAffected
  • >=21.0.0-beta1 <21.0.0-beta3
Fixed in
  • 21.0.0-beta3
GitHubopenmage/magento-ltspkg:github/openmage/magento-ltsOther threatsAffected
  • <20.18.2
  • >=21.0.0-beta1 <21.0.0-beta3
Fixed in
  • 20.18.2
  • 21.0.0-beta3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

OpenMage magento-lts versions before 20.18.2 and 21.0.0-beta pre-releases before 21.0.0-beta3 use weak methods to generate customer email confirmation keys and password-reset tokens. The keys are generated using md5(uniqid()) and uniqHash(), which are not cryptographically secure. This allows unauthenticated attackers to brute-force confirmation keys via an unrate-limited endpoint, potentially logging in as pending customers or predicting administrator reset tokens after recovering the generator state.

References

Community reviews

Loading reviews…