CVE-2022-21158
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 · uneditedA stored cross-site scripting vulnerability in marktext versions prior to v0.17.0 due to improper handling of the link (with javascript: scheme) inside the document may allow an attacker to execute an arbitrary script on the PC of the user using marktext.
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 confidenceA stored cross-site scripting vulnerability in marktext versions prior to v0.17.0 allows execution of arbitrary JavaScript code via crafted links using the javascript: scheme embedded in documents. When users open malicious documents, the embedded javascript: links execute local script execution.
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.17.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check installed MarkText versionRun 'marktext --version' from command line or look in the application About/Help section to find the version numberAffected if version displayed is earlier than v0.17.0 (e.g., v0.16.x, v0.15.x, etc.)
-
Identify documents with javascript: scheme linksSearch document files (Markdown .md files) in your local repositories or recent files for the pattern 'javascript:' using grep or a text search toolAffected if any .md files contain links beginning with 'javascript:' that could be opened in MarkText
-
Verify if documents can be opened in MarkTextOpen a document containing javascript: links in MarkText to observe if the link becomes clickable or executable within the rendered previewAffected if the javascript: links render as clickable hyperlinks and could execute local script when clicked
-
Check for recent document historyReview MarkText recent files list or check local directories for .md files received from external sources or untrusted usersAffected if you have recently opened or plan to open untrusted Markdown documents in a MarkText version prior to v0.17.0
You are affected if MarkText version is earlier than v0.17.0 AND you have opened or will open documents containing javascript: scheme links, as these links can execute arbitrary JavaScript locally.
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.17.0
Upgrade marktext to version v0.17.0 or later which properly sanitizes or blocks javascript: scheme links in documents.
Marktext v0.17.0
- Check the current version of Marktext installed
- Back up any important documents or data
- Upgrade Marktext to version 0.17.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21158 — 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-2022-21158 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