RedmineApplication

CVE-2023-47260

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-05
Fix available
A fix is available. Upgrade to 4.2.11 / 5.0.6 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.2.11 and 5.0.x before 5.0.6 allows XSS via thumbnails.

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

Redmine versions before 4.2.11 and 5.0.6 contain a stored Cross-Site Scripting (XSS) vulnerability in the thumbnail generation functionality. Attackers can embed malicious JavaScript in file attachments that are displayed as thumbnails, which then executes in the browsers of users who view those thumbnails.

MitigationUpgrade Redmine to version 4.2.11, 5.0.6, or later to patch the XSS vulnerability in thumbnail handling.

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
RedmineApplication
Affected:< 4.2.11>= 5.0.0, < 5.0.6

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 Redmine version
    Check your Redmine installation's version. This is typically displayed on the login page, in the administration panel under 'Information', or by running: ruby -e "require File.join(Rails.root, 'config/environment'); puts Redmine::VERSION.to_s" from the Redmine root directory.
    Affected if The installed version is less than 4.2.11, or is 5.0.0 through 5.0.5 (i.e., falls within < 4.2.11 or >= 5.0.0, < 5.0.6)
  2. Confirm file attachment uploads are enabled
    In Redmine, go to Administration > Settings > File uploads. Verify that 'Allow attachments' is enabled and that users can upload files to issues, documents, or wikis.
    Affected if Attachments are enabled and users can upload files to the system
  3. Check if thumbnail generation is active
    Verify that the 'Thumbnail' option is enabled for uploaded files. In Administration > Settings > File uploads, look for thumbnail-related settings. Thumbnails are automatically generated for image attachments (e.g., PNG, JPG, GIF) when displayed in issues, documents, or the file library.
    Affected if Thumbnail generation is enabled and image attachments can be viewed by users

A Redmine instance is affected if it runs a version below 4.2.11 or between 5.0.0 and 5.0.5, and has both file attachment uploads and thumbnail viewing enabled for users.

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 4.2.11 / 5.0.6 or later
Fixed in 4.2.115.0.6
Interim mitigation

Upgrade Redmine to version 4.2.11, 5.0.6, or later to patch the XSS vulnerability in thumbnail handling.

Recommended fix High confidence

Redmine 4.2.11 or 5.0.6 (depending on your current branch)

  1. Identify current Redmine version by checking the version file or application UI
  2. Back up the Redmine database and all configuration files
  3. For Redmine 4.x users: Upgrade to Redmine 4.2.11 or later
  4. For Redmine 5.0.x users: Upgrade to Redmine 5.0.6 or later
  5. After upgrade, clear any cached assets (delete tmp/cache and tmp/sessions directories)
  6. Restart the Redmine application server (Puma, Passenger, or Unicorn)
  7. Verify the upgrade was successful by checking the Redmine version in the administration panel
  8. Test that the thumbnail functionality works properly after the upgrade
Caveat Minor version upgrades typically have minimal breaking changes; review the Redmine release notes for any specific migration notes

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

Fix this in Redmine Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47260 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2023-47260 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