CVE-2023-30792
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAnchor tag hrefs in Lexical prior to v0.10.0 would render javascript: URLs, allowing for cross-site scripting on link clicks in cases where input was being parsed from untrusted sources.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-site scripting vulnerability in Lexical rich-text editor library versions prior to v0.10.0. The library fails to sanitize anchor tag href attributes, allowing javascript: URLs to be rendered. When users click on malicious links parsed from untrusted input, arbitrary JavaScript code can be executed in the victim's browser.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Lexical versionCheck your package.json file, package-lock.json, or run `npm list @lexical/react` (or the specific Lexical package you use) to see the installed version numberAffected if The installed version is lower than 0.10.0 (e.g., 0.9.x, 0.8.x, etc.)
-
Confirm Lexical is used for rendering user-supplied contentReview your codebase where Lexical is initialized and examine whether the editor content comes from untrusted sources such as user comments, form inputs, external API data, or database content that may contain HTML or link elementsAffected if The application passes untrusted or third-party content through Lexical's parser without additional sanitization
-
Inspect whether anchor tags with hrefs are processedSearch your codebase for $createLinkNode or LinkNode usage within Lexical, and check if the application deserializes or imports HTML content containing anchor tagsAffected if The app deserializes HTML with anchor tags or creates link nodes from untrusted input sources
-
Verify if URL sanitization is applied before Lexical processingExamine your data flow to see if URLs are sanitized (e.g., using a DOMPurify or similar library) before being passed to Lexical's editor state or parsed as HTMLAffected if No URL sanitization is performed on href values before they are processed by Lexical and the editor renders them as clickable links
You are affected if your installed Lexical version is below 0.10.0 AND your application uses Lexical to render or process content from untrusted sources that could contain anchor tags with javascript: URLs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.10.0
Upgrade Lexical to v0.10.0 or later which properly sanitizes URLs and blocks javascript: protocol URLs in anchor tags.
Lexical v0.10.0
- Check current Lexical version in your project (e.g., via npm list lexical or package.json)
- Update Lexical dependency to version 0.10.0 or later by running npm install lexical@^0.10.0 or yarn add lexical@^0.10.0
- Verify the upgrade was successful by checking the installed version
- Rebuild and test your application to ensure the XSS fix is working and no regressions were introduced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30792 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-30792 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data