Read the docs

Path traversal in Discourse CSV export creates directories

Priority MEDIUM 40Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · Low · High
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-7gh5-ch39-387w. Fix status from GitHub.

Summary

All Discourse versions since v2.0.0.beta8 are affected. A path traversal in the report CSV export lets moderators and admins create directories, each with a small CSV file, anywhere the Discourse process can write. A directory planted in the plugins folder makes every later Discourse boot fail, but the flaw does not allow code execution, reading files or overwriting existing files. Regular users cannot exploit it.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Impact A path traversal in the report CSV export allows staff users (moderators and admins) to create directories, each containing a small CSV file, anywhere the Discourse process can write on the server. A directory planted in the plugins folder causes every Discourse process started afterwards to fail during boot. The issue does not allow code execution, reading files, or overwriting existing files. Regular users cannot exploit it. All versions since v2.0.0.beta8 are affected. The directory creation that leads to the boot failure was introduced in v2.5.0.beta4. ### Patches The issue is patched in the latest version of Discourse. ### Workarounds - Only grant moderator and admin roles to trusted users. - Check for directories already planted in the plugins folder, and remove any incorrect entry. Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-4ADFPFMQ.

Why it matters now

Fix Fixed Discourse: 2026.11.0-latest.1, 2026.10.1, 2026.9.2 +1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—Discourse—2026.11.0-latest.1Patch availableGHSA-7gh5-ch39-387w
—Discourse>= 2026.10.0-latest2026.10.1Patch availableGHSA-7gh5-ch39-387w
—Discourse>= 2026.9.0-latest2026.9.2Patch availableGHSA-7gh5-ch39-387w
—Discourse>= 2026.7.0-latest2026.7.5Patch availableGHSA-7gh5-ch39-387w
  • Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-7gh5-ch39-387w
  • Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-7gh5-ch39-387w
  • Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-7gh5-ch39-387w
  • Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-7gh5-ch39-387w

Remediation

Upgrade Discourse to a fixed version for your release line: 2026.7.5, 2026.9.2, 2026.10.1 or 2026.11.0-latest.1. Until then, grant the moderator and admin roles only to trusted users, and check the plugins folder for planted directories and remove any incorrect entries.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-7gh5-ch39-387w Discourse Fixed in 2026.11.0-latest.1 Advisory →
  • Fix · GHSA-7gh5-ch39-387w Discourse Fixed in 2026.10.1 Advisory →
  • Fix · GHSA-7gh5-ch39-387w Discourse Fixed in 2026.9.2 Advisory →
  • Fix · GHSA-7gh5-ch39-387w Discourse Fixed in 2026.7.5 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-7gh5-ch39-387w

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences