dbcve.org
RedmineApplication

CVE-2022-44637

MEDIUM · 6.1 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to 4.2.9 / 5.0.4 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.9 and 5.0.x before 5.0.4 allows persistent XSS in its Textile formatter due to improper sanitization in Redcloth3 Textile-formatted fields. Depending on the configuration, this may require login as a registered user.

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.9 and 5.0.4 contain a persistent XSS vulnerability in the Textile formatter (Redcloth3) where Textile-formatted fields are not properly sanitized, allowing attackers to inject malicious scripts that execute in other users' browsers.

MitigationUpgrade Redmine to version 4.2.9, 5.0.4, or later. Until upgraded, restrict or disable Textile formatting in user-editable fields or implement additional input validation.

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.9>= 5.0.0, < 5.0.4

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
    Access the Redmine administration panel: navigate to Administration > Information, or inspect the config/version.rb file in the Redmine installation directory, or check the version in your Gemfile.lock (look for the 'redmine' or 'Redmine' gem entry)
    Affected if The version is below 4.2.9, or is 5.0.0 through 5.0.3
  2. Determine if Textile formatting is enabled
    In the Redmine administration panel, go to Administration > Settings > Text formatting (or Project > Settings > Information on older versions). Look for the available text formatters. Check whether 'Textile' or 'Redcloth' is listed as an available format.
    Affected if Textile/Redcloth is listed as an available text formatting option
  3. Identify user-editable fields using Textile
    Review which fields allow rich text formatting. Common locations include: issue descriptions, issue notes, wiki pages, news entries, and document descriptions. Check the settings for each project under Project > Settings > Information to see which text format is selected for description fields.
    Affected if Any user-editable field (such as issue descriptions, wiki pages, or comments) is configured to use Textile formatting
  4. Verify Redcloth3 gem version (optional)
    If you have command-line access, run 'gem list redcloth3' or check your Gemfile.lock for the redcloth3 gem version
    Affected if The redcloth3 gem version is older than the version bundled with patched Redmine releases

You are affected if your Redmine version is below 4.2.9 or between 5.0.0 and 5.0.3, AND Textile/Redcloth formatting is enabled for any user-editable text fields in your installation.

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.9 / 5.0.4 or later
Fixed in 4.2.95.0.4
Interim mitigation

Upgrade Redmine to version 4.2.9, 5.0.4, or later. Until upgraded, restrict or disable Textile formatting in user-editable fields or implement additional input validation.

Recommended fix High confidence

Redmine 4.2.9+ or 5.0.4+ (recommended: latest stable 5.x release)

  1. Backup your Redmine database and all files before proceeding
  2. Identify your current Redmine version in Administration > Information
  3. If running Redmine 4.2.x: upgrade to version 4.2.9 or later
  4. If running Redmine 5.0.x: upgrade to version 5.0.4 or later
  5. Alternatively, upgrade to the latest stable Redmine release (5.1.0 or higher if available)
  6. Test the upgrade in a staging environment before deploying to production
  7. Deploy the upgraded version to production
Caveat Minor version upgrades may introduce plugin compatibility issues; test thoroughly before production deployment

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

Fix this in Redmine Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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