CVE-2026-128047: OpenMage magento-lts before 20.18.2 Account Takeover via Predictable Confirmation Key
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: OpenMage magento-lts 20.18.2, 21.0.0-beta3.
Low priority for now. Upgrade to OpenMage magento-lts 20.18.2, 21.0.0-beta3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
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.
- Published
- Nov 13, 2026
- Updated
- Nov 13, 2026
- EPSS
- —
- CWE
- CWE-330
Report tools
Action score
36
Low priority for now.
- CVSS
- 36 / 40 · 9.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 9.2
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
OpenMage magento-lts
- 20.18.2, 21.0.0-beta3not affected
- before 20.18.2affected · semver
- 21.0.0-beta1 and later · before 21.0.0-beta3affected · semver
Same product
openmage: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-128049OpenMage Magento LTS before 20.18.2 CSRF via OAuth Authorization Confirm37Monitor
- CVE-2026-42155Magento LTS: Weak API Session ID — Predictable MD5 of Time-Derived Inputs37Monitor
- CVE-2026-128046OpenMage magento-lts 20.17.0 before 20.18.2 Unrestricted File Upload RCE via Custom Options36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-128044Nov 13, 2026 · OpenMage magento-lts before 20.18.2 OAuth Callback URL Allowlist Bypass34Monitor
- ← EarlierCVE-2026-128045Nov 13, 2026 · OpenMage Magento-LTS before 20.18.2 Authorization Bypass via Forgeable RSS Order Key27Monitor
- Later →CVE-2026-128048Nov 13, 2026 · OpenMage magento-lts before 20.18.2 Information Disclosure via Email Template getConfig27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| OpenMage magento-lts | 20.18.2 | Vendor (CNA) |
| OpenMage magento-lts | 21.0.0-beta3 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 13, 2026same day
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- alimonyreporter
- Abhi-Hackzreporter
- hariprasanth9317-techfinder
- philipsorensenremediation developer
- colinmollenhourremediation developer
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-330 · Use of Insufficiently Random ValuesCVSS vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.