dbcve.org
Jira Software Data CenterApplication · Atlassian

CVE-2021-41310

MEDIUM · 6.1 CVSS v3.1 Published 2021-11-01
Fix available
A fix is available. Upgrade to 8.5.19 / 8.13.11 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
Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to inject arbitrary HTML or JavaScript via a Cross-Site Scripting (XSS) vulnerability in the Associated Projects feature (/secure/admin/AssociatedProjectsForCustomField.jspa). The affected versions are before version 8.5.19, from version 8.6.0 before 8.13.11, and from version 8.14.0 before 8.19.1.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in Atlassian Jira Server and Data Center's Associated Projects feature (/secure/admin/AssociatedProjectsForCustomField.jspa). Anonymous remote attackers can inject arbitrary HTML or JavaScript into custom field configurations, which then executes in the browsers of other users viewing those configurations.

MitigationUpgrade Jira to version 8.5.19, 8.13.11, 8.19.1 or later. Alternatively, restrict access to the affected admin page or implement WAF rules to block XSS attack patterns.

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
Jira Software Data CenterApplication
Affected:< 8.5.19>= 8.6.0, < 8.13.11>= 8.14.0, < 8.19.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. Check Jira version
    Log in as an administrator, go to Settings > System > About (or /secure/admin/About.jspa) to view the installed Jira version number
    Affected if The version falls within < 8.5.19, >= 8.6.0 and < 8.13.11, or >= 8.14.0 and < 8.19.1
  2. Verify access to the vulnerable endpoint
    Navigate to /secure/admin/AssociatedProjectsForCustomField.jspa while logged in. If the page loads without a permission denied error, the endpoint is accessible
    Affected if The page loads and allows configuration of custom field associations
  3. Identify custom fields in use
    Go to Settings > Issues > Custom Fields (or /secure/admin/ViewCustomFields.jspa) to list all custom fields defined in the system
    Affected if Any custom fields exist in the Jira instance, as these are the targets for malicious payload injection

A Jira instance is affected if its version is within the vulnerable ranges AND the Associated Projects admin page is accessible to users who can configure custom fields.

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 8.5.19 / 8.13.11 / 8.19.1 or later
Fixed in 8.5.198.13.118.19.1
Interim mitigation

Upgrade Jira to version 8.5.19, 8.13.11, 8.19.1 or later. Alternatively, restrict access to the affected admin page or implement WAF rules to block XSS attack patterns.

Recommended fix High confidence

8.19.1 (or latest 8.x LTS release)

  1. 1. Identify the current Jira Software Data Center version by navigating to Jira Administration > System > System Info
  2. 2. Determine the appropriate upgrade path based on current version: if < 8.5.19, upgrade to 8.5.19 or later; if >= 8.6.0 and < 8.13.11, upgrade to 8.13.11 or later; if >= 8.14.0 and < 8.19.1, upgrade to 8.19.1 or later
  3. 3. Review Jira upgrade documentation and release notes for the target version
  4. 4. Perform a full backup of the Jira database and home directory
  5. 5. Test the upgrade in a staging or development environment first
  6. 6. Schedule a maintenance window and apply the upgrade during low-usage period
  7. 7. After upgrade, verify the patch is applied by checking the Jira version matches the fixed release
  8. 8. Confirm the XSS vulnerability in /secure/admin/AssociatedProjectsForCustomField.jspa is no longer exploitable
Caveat Standard Jira upgrade considerations apply - review migration notes for any configuration or plugin changes required; always test in non-production first

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

Fix this in Jira Software Data Center Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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