dbcve.org
Editor CoreApplication · Atlassian

CVE-2019-20903

MEDIUM · 5.4 CVSS v3.1 Published 2020-10-01
Fix available
A fix is available. Upgrade to 113.1.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The hyperlinks functionality in atlaskit/editor-core in before version 113.1.5 allows remote attackers to inject arbitrary HTML or JavaScript via a Cross-Site Scripting (XSS) vulnerability in link targets.

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

The hyperlinks functionality in Atlassian's atlaskit/editor-core before version 113.1.5 contains a stored Cross-Site Scripting (XSS) vulnerability. Attackers can inject arbitrary HTML or JavaScript through malicious link targets, which are then executed in the context of other users' browsers when they view or interact with the hyperlinks.

MitigationUpgrade atlaskit/editor-core to version 113.1.5 or later, which contains the fix for this vulnerability. Additionally, implement output encoding and content security policy headers as defense-in-depth measures.

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
Editor CoreApplication
Affected:< 113.1.5

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

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

  1. Identify if Atlaskit/editor-core is installed
    Check your package.json dependencies or run 'npm list @atlaskit/editor-core' to see if the library is present in your project
    Affected if The package is listed in dependencies
  2. Determine the installed version of Atlaskit/editor-core
    Run 'npm list @atlaskit/editor-core --depth=0' or check the version in node_modules/@atlaskit/editor-core/package.json
    Affected if The installed version is lower than 113.1.5 (e.g., 113.1.4, 113.0.0, etc.)
  3. Verify the hyperlinks feature is in use
    Review your application code to confirm the editor-core is being used with hyperlink functionality enabled, typically through editor configuration or the @atlaskit/editor-plugin-hyperlink package
    Affected if The editor with hyperlink functionality is rendering user-generated content

You are affected if Atlaskit/editor-core version lower than 113.1.5 is installed and your application uses the editor to render or preview hyperlinks containing user-supplied link targets.

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 113.1.5 or later
Fixed in 113.1.5
Interim mitigation

Upgrade atlaskit/editor-core to version 113.1.5 or later, which contains the fix for this vulnerability. Additionally, implement output encoding and content security policy headers as defense-in-depth measures.

Fix this in Editor Core Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-20903 — 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-2019-20903 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