CVE
magento-lts stored XSS in TinyMCE WYSIWYG editor
Affects OpenMage magento-lts before 20.2.0 when the TinyMCE WYSIWYG editor is enabled in the configuration. Fixed in 20.2.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 20.2.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. OpenMage magento-lts versions before 20.2.0 TinyMCE WYSIWYG editor feature enabled in the configuration
- 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? →
- 16/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? →
- Specific setups only
- 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 versions before 20.2.0 contain a stored cross-site scripting flaw in the TinyMCE WYSIWYG editor, which fails to filter scripts in specially crafted HTML tags. An attacker who can reach the application over the network and must log in with high privileges can inject a malicious image element that runs scripts in the browsers of users who view the rendered content, which requires some user interaction.
Read the original description
OpenMage magento-lts before 20.2.0 contains a stored cross-site scripting vulnerability because the TinyMCE WYSIWYG editor fails to filter scripts in specially crafted HTML tags. Attackers can inject an img element with a malicious onmouseover attribute to execute scripts in the browsers of users viewing the rendered content.
Who should check
Teams running OpenMage magento-lts before 20.2.0 with the TinyMCE WYSIWYG editor enabled
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
OpenMage magento-lts versions before 20.2.0 TinyMCE WYSIWYG editor feature enabled in the configurationUpgrade to a fixed version: 20.2.0.
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-2023-54423 (OpenMage magento-lts before 20.2.0 Stored XSS via TinyMCE WYSIWYG Editor), 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-2023-54423 (entry last updated 2026-11-13):
Affected:
- OpenMage magento-lts: fixed in 20.2.0
Fixed versions: 20.2.0.
Conditions (all must be true for the bug to be hit):
- OpenMage magento-lts versions before 20.2.0 (source: https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.2.0-stored-xss-via-tinymce-wysiwyg-editor)
- TinyMCE WYSIWYG editor feature enabled in the configuration (source: https://github.com/OpenMage/magento-lts/security/advisories/GHSA-9j5w-2cqc-cwj9)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, a user action.
CISA KEV: CVE-2023-54423 is not listed as of cve.now's last read.
This KEV status is for CVE-2023-54423 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-9j5w-2cqc-cwj9
- https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.2.0-stored-xss-via-tinymce-wysiwyg-editor
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-2023-54423
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-2023-54423"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- OpenMage magento-lts
fixed in 20.2.0
Evidence 4
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-2023-54423
Is CVE-2023-54423 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?
An attacker can inject an img element with a malicious onmouseover attribute, so scripts run in the browsers of users who view the rendered content (stored XSS).Source: vulncheck.com, github.com
Which versions are affected by CVE-2023-54423?
magento-lts: before 20.2.0.Source: cve.now feed data
Am I affected, and how do I check?
OpenMage magento-lts versions before 20.2.0 are in scope, but only where the TinyMCE WYSIWYG editor feature is enabled in the configuration. To check, look at the WYSIWYG editor setting in the store configuration and confirm the installed version.Source: vulncheck.com, github.com
How do I fix CVE-2023-54423?
Upgrade magento-lts to 20.2.0 or later, which is the fixed version listed for this vulnerability.Source: vulncheck.com, github.com