dbcve.org
Youtrack IntegrationApplication · Jetbrains

CVE-2019-10100

CRITICAL · 9.8 CVSS v3.0 Published 2019-07-03
Fix available
A fix is available. Upgrade to 1.8.1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
In JetBrains YouTrack Confluence plugin versions before 1.8.1.3, it was possible to achieve Server Side Template Injection. The attacker could add an Issue macro to the page in Confluence, and use a combination of a valid id field and specially crafted code in the link-text-template field to execute code remotely.

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

Server Side Template Injection (SSTI) vulnerability in JetBrains YouTrack Confluence plugin versions before 1.8.1.3 allows remote code execution. Attackers can exploit this by inserting an Issue macro into a Confluence page and providing a valid id field combined with malicious code in the link-text-template field.

MitigationUpgrade the YouTrack Confluence plugin to version 1.8.1.3 or later to remediate the SSTI vulnerability.

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
Youtrack IntegrationApplication
Affected:< 1.8.1.3

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 YouTrack Confluence plugin is installed
    Log in to Confluence as administrator and navigate to Confluence Administration > Manage add-ons or Plugins. Look for YouTrack Integration or YouTrack plugin in the list of installed add-ons.
    Affected if The YouTrack plugin appears in the installed add-ons list
  2. Check the installed version of the YouTrack plugin
    In the Manage add-ons screen, locate the YouTrack Integration plugin and note the version number displayed in the plugin details or version column.
    Affected if The version number is lower than 1.8.1.3 (for example, 1.8.0, 1.7.x, etc.)
  3. Verify the plugin is enabled
    In the Manage add-ons screen, confirm the YouTrack plugin status shows as Enabled or Enabled (bundled).
    Affected if The plugin is enabled and the version is below 1.8.1.3
  4. Check for the Issue macro usage
    Review Confluence pages for the presence of the YouTrack Issue macro by searching for {youtrack-issue} or checking page content for the macro in Confluence storage format or via the macro browser.
    Affected if The plugin version is vulnerable AND the Issue macro has been used on any Confluence page

You are affected if the YouTrack Confluence plugin version is below 1.8.1.3 and the plugin is enabled in your Confluence instance.

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.

dbcve · scoped
Upgrade available Upgrade to 1.8.1.3 or later
Fixed in 1.8.1.3
Interim mitigation

Upgrade the YouTrack Confluence plugin to version 1.8.1.3 or later to remediate the SSTI vulnerability.

Recommended fix High confidence

YouTrack Confluence plugin version 1.8.1.3 or later

  1. 1. Identify the current version of the YouTrack Confluence plugin by navigating to Confluence administration > Manage add-ons > YouTrack Integration
  2. 2. If the installed version is before 1.8.1.3, locate the plugin upgrade option in the Manage add-ons section
  3. 3. Upgrade the YouTrack Confluence plugin to version 1.8.1.3 or later
  4. 4. Restart the Confluence service if required by the upgrade process
  5. 5. Verify the upgrade was successful by confirming the installed version displays 1.8.1.3 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Youtrack Integration Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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