LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36306: Redmine before 4.0.7 and 4.1.x before 4.1.1 has XSS via the back_url field.

Redmine before 4.0.7 and 4.1.x before 4.1.1 has XSS via the back_url field.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a cross-site scripting flaw in Redmine’s handling of the back_url field. A vulnerable Redmine site could let attacker-controlled script run in a user’s browser within the Redmine context. The supplied sources provide no CVSS score or active exploitation evidence.

Executive priority

Treat this as a targeted hygiene fix for Redmine environments. It is not supported as actively exploited by the supplied evidence, but XSS in project management tooling can still affect users and sensitive project data.

Technical view

CVE-2020-36306 affects Redmine before 4.0.7 and Redmine 4.1.x before 4.1.1. The issue is XSS via the back_url field. The bundle does not include CWE, CVSS vector, detailed prerequisites, or proof-of-concept information.

Likely exposure

Organizations running self-hosted Redmine below 4.0.7, or 4.1.x below 4.1.1, are the likely exposed population. Internet-facing Redmine instances have higher business exposure.

Exploitation context

The provided sources identify an XSS condition but do not state active exploitation. The CVE is not listed as KEV in the supplied bundle, so exploitation should not be assumed.

Researcher notes

The public bundle is sparse: no CVSS, CWE, exploit details, or prerequisites are provided. Analysis should stay limited to affected Redmine versions and the back_url XSS condition unless vendor advisories add detail.

Mitigation direction

  • Upgrade Redmine to 4.0.7, 4.1.1, or a later supported release.
  • Apply the relevant Debian LTS Redmine security update where Debian packages are used.
  • Check Redmine’s security advisory page for version-specific vendor guidance.
  • Prioritize externally reachable Redmine systems and high-trust project management environments.

Validation and detection

  • Inventory all Redmine instances and record exact application versions.
  • Confirm vulnerable versions are upgraded beyond the affected release ranges.
  • Check package manager history for the Debian LTS Redmine security update if applicable.
  • Review application logs for suspicious back_url-related XSS indicators without reproducing payloads.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-36306 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.