CVE-2023-32061

What it is

Discourse is an open source discussion platform. Prior to version 3.0.4 of the `stable` branch and version 3.1.0.beta5 of the `beta` and `tests-passed` branches, the lack of restrictions on the iFrame tag makes it easy for an attacker to exploit the vulnerability and hide subsequent comments from other users. This issue is patched in version 3.0.4 of the `stable` branch and version 3.1.0.beta5 of the `beta` and `tests-passed` branches. There are no known workarounds.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2023-06-13 22:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 05:57 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 5.4 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2023-06-13 22:15 UTC

Last modified

2026-06-17 05:57 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-863 · Incorrect authorization

Record status

Modified

Affected

• Discourse < 3.0.4
• Discourse 3.1.0

Attack profile CVSS 3.1 · 5.4

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2023-32061.md and follow it. Check whether this project is affected by CVE-2023-32061. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge