Read the docs

QuoteComparer skips Guardian: any user can read PMs via quote-modified

Priority LOW 38Published · Updated

Key facts

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

No CVSS vector from any source. Fix status from GitHub.

Summary

Discourse compares quoted text against the original post when a post containing a quote is cooked, and marks mismatches with quote-modified or quote-post-not-found CSS classes. This comparison loaded the parent post by topic id and post number without a Guardian permission check, so the result reflected posts the quoting user cannot see. Any logged-in user could post a quote targeting an arbitrary topic id and post number, including private messages and posts in restricted categories, and read their contents from the resulting CSS classes. CISA's KEV catalog does not list this vulnerability, and the advisory references no exploit link.

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

Description from the GitHub advisory

### Impact Information disclosure. When a post containing a `[quote]` is cooked, Discourse compares the quoted text against the original post and marks the block with a `quote-modified` or `quote-post-not-found` CSS class. This comparison loaded the parent post by topic id and post number with no Guardian check, so the result reflected posts the quoting user cannot see. Any logged-in user could post a quote targeting an arbitrary topic id and post number, including private messages and posts in restricted categories. ### Patches incoming ### Workarounds none

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-vrgg-p6pm-xx4w
—Discourse>= 2026.10.0-latest2026.10.1Patch availableGHSA-vrgg-p6pm-xx4w
—Discourse>= 2026.9.0-latest2026.9.2Patch availableGHSA-vrgg-p6pm-xx4w
—Discourse>= 2026.7.0-latest2026.7.5Patch availableGHSA-vrgg-p6pm-xx4w
  • Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-vrgg-p6pm-xx4w
  • Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-vrgg-p6pm-xx4w
  • Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-vrgg-p6pm-xx4w
  • Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-vrgg-p6pm-xx4w

Remediation

Upgrade Discourse to 2026.11.0-latest.1, 2026.10.1, 2026.9.2 or 2026.7.5, depending on the release line. The advisory lists no workaround.

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

  • Fix · GHSA-vrgg-p6pm-xx4w Discourse Fixed in 2026.11.0-latest.1 Advisory →
  • Fix · GHSA-vrgg-p6pm-xx4w Discourse Fixed in 2026.10.1 Advisory →
  • Fix · GHSA-vrgg-p6pm-xx4w Discourse Fixed in 2026.9.2 Advisory →
  • Fix · GHSA-vrgg-p6pm-xx4w Discourse Fixed in 2026.7.5 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-vrgg-p6pm-xx4w

References

Sources

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