Read the docs

Discourse Automation script lets users join automatic groups

Priority MEDIUM 44Published · Updated

Key facts

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

Attack profile from CVSS 3.1 · GHSA-v39w-j36j-fh6q. Fix status from GitHub.

Summary

The Automation plugin in Discourse adds users to a group chosen by a user field, through its "Add user to group through User Custom Field" script. When that script uses a free-text user field, any user who can create an account can select an automatic group such as admins or moderators. Membership lets them edit others' posts, delete topics and read restricted content.

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

Description from the GitHub advisory

# Impact In the bundled Automation plugin, the "Add user to group through User Custom Field" script adds a user to a group selected by the value of a user field. When the script used a free-text user field, a user could make it select an automatic group, such as admins or moderators. Any person who can create an account could do this. With the default settings, membership in these groups lets the user edit other users' posts, delete topics, and read content restricted to these groups. The user does not get the admin or moderator role, and cannot open the admin interface. Only sites that enabled the Automation plugin and configured this script on a free-text user field are affected. # Workarounds - Disable the automation, or - Change the user field that the automation uses to a dropdown. To find affected accounts, examine the group logs of the automatic groups for members that the system user added. # After the update The script no longer adds users to automatic groups. It can still add users to any other group that has a full name, so use it with a free-text field only for groups that any user may join. Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-6JM1BR5X.

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

Remediation

Discourse is fixed in 2026.11.0-latest.1, 2026.10.1, 2026.9.2 and 2026.7.5, so upgrade to the fixed version for your release line. Until then, disable the automation or change the user field it uses to a dropdown.

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

  • Fix · GHSA-v39w-j36j-fh6q Discourse Fixed in 2026.11.0-latest.1 Advisory →
  • Fix · GHSA-v39w-j36j-fh6q Discourse Fixed in 2026.10.1 Advisory →
  • Fix · GHSA-v39w-j36j-fh6q Discourse Fixed in 2026.9.2 Advisory →
  • Fix · GHSA-v39w-j36j-fh6q Discourse Fixed in 2026.7.5 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-v39w-j36j-fh6q

References

Sources

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