CVE-2023-47258
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.11 and 5.0.x before 5.0.6 allows XSS in a Markdown formatter.
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 before 4.2.11 and 5.0.6 contains a cross-site scripting (XSS) vulnerability in its Markdown formatter. Attackers can inject malicious scripts through specially crafted Markdown content that gets rendered without proper sanitization, potentially executing in the browsers of users who view the 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.11>= 5.0.0, < 5.0.6CVSS 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.
-
Locate your Redmine version numberAccess the Redmine administration panel or check the version file in your Redmine installation directoryAffected if The version displayed is less than 4.2.11, or is 5.0.0 through 5.0.5
-
Identify the text formatting engine in useNavigate to Redmine administration settings and inspect the default text formatting preference for issues, wiki pages, and documentsAffected if Markdown formatting is enabled as the default or for the specific content area being reviewed
-
Verify Markdown content rendering behaviorCreate or view a test issue, wiki page, or document using Markdown syntax in your Redmine instanceAffected if Markdown content renders without visible sanitization errors or warnings, indicating the vulnerable formatter is active
You are affected if your Redmine version is below 4.2.11 or falls between 5.0.0 and 5.0.5, and the Markdown formatter is enabled for rendering user-supplied content.
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.115.0.6
Upgrade Redmine to version 4.2.11 or 5.0.6 or later to incorporate the security fix for the Markdown formatter XSS vulnerability.
Redmine 4.2.11 (for 4.2.x users) or Redmine 5.0.6 (for 5.0.x users)
- 1. Back up your Redmine database and all files
- 2. Identify your current Redmine version (run: ruby bin/rails runner 'puts Redmine::VERSION.string')
- 3. If running 4.2.x (below 4.2.11): Plan upgrade to Redmine 4.2.11
- 4. If running 5.0.x (below 5.0.6): Plan upgrade to Redmine 5.0.6
- 5. Download the appropriate fixed release from www.redmine.org/projects/redmine/wiki/Download
- 6. Extract the new version to a temporary location
- 7. Copy the config/database.yml and any custom configuration files from your current installation
- 8. Stop the Redmine application server
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-47258 — 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-2023-47258 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