CVE-2022-44031
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 · uneditedRedmine before 4.2.9 and 5.0.x before 5.0.4 allows persistent XSS in its Textile formatter due to improper sanitization of the blockquote syntax in Textile-formatted fields.
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 confidenceRedmine versions before 4.2.9 and 5.0.4 contain a persistent XSS vulnerability in the Textile formatter. The blockquote syntax in Textile-formatted fields is not properly sanitized, allowing attackers to inject malicious JavaScript that executes when other users view the affected content.
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< 4.2.9>= 5.0.0, < 5.0.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Redmine versionAccess the Redmine admin interface (Administration > Information) or check the VERSION file in the Redmine root directory to determine the installed version number.Affected if The installed version is before 4.2.9, or is 5.0.0 through 5.0.3.
-
Confirm Textile formatter is in useReview Redmine custom field configurations and project settings to identify which fields have the Textile formatter enabled as the text formatting option.Affected if Textile formatting is enabled on any custom fields, issue descriptions, or other user-editable text areas that are accessible to untrusted users.
-
Check field visibility to untrusted usersExamine which Textile-enabled fields are visible or editable by non-admin users, such as custom fields on issues, documents, or news entries.Affected if Textile-formatted fields are accessible to users who are not trusted administrators.
A user is affected if their Redmine version falls below 4.2.9 or is between 5.0.0 and 5.0.3 AND Textile formatting is enabled on fields accessible to untrusted users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.2.95.0.4
Upgrade Redmine to version 4.2.9 or later, or 5.0.4 or later. Until upgraded, restrict or disable Textile formatting in user-accessible fields.
Redmine 4.2.9 for 4.x users; Redmine 5.0.4 for 5.0.x users
- Backup your Redmine database before upgrading
- Backup your Redmine files and configuration (config/database.yml, config/configuration.yml)
- Download Redmine 4.2.9 (if on 4.x) or 5.0.4 (if on 5.0.x) from www.redmine.org/projects/redmine/wiki/Download
- Extract the new version to your Redmine installation directory
- Run bundle install --without development test rmagick to install dependencies
- Run rake db:migrate RAILS_ENV=production to apply database migrations
- Run rake tmp:cache:clear RAILS_ENV=production to clear cached files
- Restart your Redmine application server (Puma, Unicorn, or Passenger)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44031 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-44031 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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