dbcve.org
Debian LinuxOperating system · Debian

CVE-2020-36307

MEDIUM · 6.1 CVSS v3.1 Published 2021-04-06
Fix available
A fix is available. Upgrade to 4.0.7 / 4.1.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
Redmine before 4.0.7 and 4.1.x before 4.1.1 has stored XSS via textile inline links.

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

Stored XSS vulnerability in Redmine's textile inline link parsing. Attackers can inject malicious JavaScript through crafted textile-formatted links that persist in the system and execute when other users view the content.

MitigationUpgrade Redmine to version 4.0.7, 4.1.1, or later to obtain the patch that properly sanitizes textile inline link input.

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
Debian LinuxOperating system
Affected:= 9.0
RedmineApplication
Affected:< 4.0.7>= 4.1.0, < 4.1.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 installed Redmine version
    Run 'bundle exec rake --version' from the Redmine directory, or check the VERSION file in the Redmine root, or look at the version displayed in the Redmine Administration > Information page
    Affected if The version is less than 4.0.7, or is exactly 4.1.0 (versions 4.1.1 and later are patched)
  2. Confirm Textile formatting is in use
    Navigate to Administration > Settings > General and check the 'Text formatting' option. Alternatively, check config/settings.yml for the default_text_formatting setting
    Affected if Textile is selected as the default or project-specific text formatter, enabling the vulnerable parsing path
  3. Identify content using Textile markup
    Examine project wikis, issues, documents, and news entries. Check if any content contains Textile-formatted links such as '"link text":url' syntax which triggers the vulnerable inline link parser
    Affected if User-contributed content with Textile link syntax exists in the system, creating potential XSS injection points

You are affected if your Redmine version is below 4.0.7 or exactly 4.1.0, and Textile formatting is enabled or used in any content areas where users can submit textile-formatted links.

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 4.0.7 / 4.1.1 or later
Fixed in 4.0.74.1.1
Interim mitigation

Upgrade Redmine to version 4.0.7, 4.1.1, or later to obtain the patch that properly sanitizes textile inline link input.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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