# CVE-2026-72731: Discourse: Strip SQL comments and use non-recursive parameter interpolation in Data Explorer

> Attackers can execute arbitrary SQL queries to read any database table via crafted parameter values in Data Explorer queries.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** BIT-discourse-2026-72731, GHSA-wm63-83xp-59r5

## What is CVE-2026-72731?

CVE-2026-72731 is a high-severity SQL injection vulnerability in discourse, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Discourse is an open-source discussion platform. From 2026.1.0-latest until 2026.1.7, 2026.6.2, 2026.7.1, and 2026.8.0-latest.1, anyone able to run a parameterized Data Explorer query, including non-staff members of a group a query is shared with, could craft parameter values that escaped the intended query and executed arbitrary SQL through plugins/discourse-data-explorer/lib/discourse_data_explorer/data_explorer.rb and plugins/discourse-data-explorer/lib/discourse_data_explorer/workflows/sql_action/v1.rb. Recursive parameter interpolation allowed one parameter value to introduce another parameter, and parameter declarations in SQL comments could be used to inject a statement. Queries run in a read-only transaction, so data could not be modified, but any table could be read. This issue is fixed in versions 2026.1.7, 2026.6.2, 2026.7.1, and 2026.8.0-latest.1.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-72731?

1 open source package ship an affected version, including discourse.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `discourse` | Bitnami | All versions | 2026.1.7, 2026.6.2, 2026.7.1 |

## How do I fix CVE-2026-72731?

Upgrade discourse to a fixed version for your release line: 2026.1.7, 2026.6.2 or 2026.7.1.

## Is CVE-2026-72731 being exploited?

There is no known exploitation of CVE-2026-72731 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72731 and fix it if it is affected.

What it is: CVE-2026-72731 is a high-severity SQL injection vulnerability in discourse, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72731 in the wild and no public exploit code.

Affected packages and fixed versions:
- discourse (Bitnami): affected all versions; fixed in 2026.1.7, 2026.6.2, 2026.7.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72731/ (Markdown: https://insights.sbomify.com/CVE-2026-72731/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72731
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72731
- OSV: https://osv.dev/vulnerability/CVE-2026-72731

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72731/
Summaries are generated and may contain mistakes; the official description above is the record.