dbcve.org
Ckeditor 5 LinkApplication · Ckeditor

CVE-2018-11093

MEDIUM · 6.1 CVSS v3.1 Published 2018-05-22
Fix available
A fix is available. Upgrade to 10.0.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross-site scripting (XSS) vulnerability in the Link package for CKEditor 5 before 10.0.1 allows remote attackers to inject arbitrary web script through a crafted href attribute of a link (A) element.

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 confidence

Cross-site scripting (XSS) vulnerability in the Link package for CKEditor 5 versions before 10.0.1 allows remote attackers to inject arbitrary web script through a crafted href attribute of a link (A) element.

MitigationUpgrade CKEditor 5 to version 10.0.1 or later to patch the XSS vulnerability in the Link package.

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
Ckeditor 5 LinkApplication
Affected:< 10.0.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify CKEditor 5 installation
    Check your project's package.json file, node_modules directory, or the JavaScript files loaded in your application for CKEditor 5 presence
    Affected if CKEditor 5 is present in your application
  2. Verify Link package is enabled
    Check if the '@ckeditor/ckeditor5-link' package is listed in your dependencies (package.json) or if the link feature is loaded in your CKEditor 5 configuration
    Affected if The Link package is installed and enabled in your CKEditor 5 editor instance
  3. Determine CKEditor 5 version
    Check the version field in your package.json for '@ckeditor/ckeditor5' or '@ckeditor/ckeditor5-link', or inspect the built ckeditor5-link.js file for version information
    Affected if The installed version is earlier than 10.0.1
  4. Confirm link editing is accessible
    Determine whether users have access to the link plugin functionality in the WYSIWYG editor (via toolbar button or direct link insertion)
    Affected if Users can create or edit links in the editor and the version is below 10.0.1

You are affected if CKEditor 5 with the Link package version below 10.0.1 is installed and the link editing feature is accessible to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 10.0.1 or later
Fixed in 10.0.1
Interim mitigation

Upgrade CKEditor 5 to version 10.0.1 or later to patch the XSS vulnerability in the Link package.

Fix this in Ckeditor 5 Link Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-11093 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-11093 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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