CVE
magento-lts account takeover via predictable customer confirmation keys
Affects OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 through beta2 when customer email confirmation is enabled, which is the default. Fixed in 20.18.2 and 21.0.0-beta3.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 20.18.2, 21.0.0-beta3
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 31/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OpenMage magento-lts before 20.18.2 and 21.0.0-beta pre-releases before 21.0.0-beta3 generate customer email-confirmation keys with md5(uniqid()) and customer and administrator password-reset tokens with the non-cryptographic uniqHash(). Unauthenticated attackers can brute-force the roughly 20-bit confirmation key via the unrate-limited confirmAction endpoint to log in as pending customers, or predict administrator reset tokens after recovering generator state.
Who should check
Teams running OpenMage magento-lts before 20.18.2, or 21.0.0 beta pre-releases before 21.0.0-beta3, with customer email confirmation enabled (on by default).
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.2/10CVSS 9.2
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 20.18.2, 21.0.0-beta3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128047 (OpenMage magento-lts before 20.18.2 Account Takeover via Predictable Confirmation Key), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128047 (entry last updated 2026-11-13):
Affected:
- OpenMage magento-lts: fixed in 20.18.2
- OpenMage magento-lts: from 21.0.0-beta1, fixed in 21.0.0-beta3
Fixed versions: 20.18.2, 21.0.0-beta3.
Conditions (all must be true for the bug to be hit):
- Customer email confirmation is enabled, which is the default, so the weak confirmation key is on the default registration path. (source: https://github.com/OpenMage/magento-lts/security/advisories/GHSA-7j66-6mw7-rgfx)
- Predicting password-reset tokens requires recovering the generator state. (source: https://github.com/OpenMage/magento-lts/security/advisories/GHSA-7j66-6mw7-rgfx)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-128047 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128047 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/OpenMage/magento-lts/security/advisories/GHSA-7j66-6mw7-rgfx
- https://github.com/OpenMage/magento-lts/commit/4a8d91c692524de4a07e70af5367b6cb67a9516d
- https://github.com/OpenMage/magento-lts/commit/9f5a1c3cf63f5cf6ac9f90b041a97a474cea04c2
- https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.18.2-account-takeover-via-predictable-confirmation-key
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128047
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128047"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- OpenMage magento-lts
fixed in 20.18.2
- OpenMage magento-lts
From 21.0.0-beta1 · fixed in 21.0.0-beta3
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-128047
Is CVE-2026-128047 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The customer email confirmation key is predictable, so account confirmation can be abused to take over a customer account without a password. Predicting password-reset tokens can also reach administrator accounts, which can lead to full store compromise, if the generator state can be recovered.Source: github.com
Which versions are affected by CVE-2026-128047?
magento-lts: before 20.18.2. magento-lts: from 21.0.0-beta1 before 21.0.0-beta3.Source: cve.now feed data
Am I affected, and how do I check?
Versions of magento-lts before 20.18.2, and 21.0.0-beta1 through 21.0.0-beta2. The weak key sits on the default registration path, so check whether customer email confirmation is enabled in the store configuration and which magento-lts version is installed.Source: github.com
How do I fix CVE-2026-128047?
Upgrade to 20.18.2 or, on the 21.0.0 beta line, to 21.0.0-beta3. The advisory names no separate patch ids.Source: github.com