# CVE-2025-53532: giscus allows unauthorized discussion creation

> An attacker can create unauthorized discussions on any repository using giscus, potentially spamming or disrupting community interactions.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2025
- **Updated:** 7 Jul 2025
- **Also known as:** GHSA-w6vg-v24f-4vm3

## What is CVE-2025-53532?

CVE-2025-53532 is a medium-severity missing authorization vulnerability in giscus, published on 7 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

giscus is a commenting system powered by GitHub Discussions. A bug in giscus' discussions creation API allowed an unauthorized user to create discussions on any repository where giscus is installed. This affects the server-side part of giscus, which is provided via http://giscus.app or your own self-hosted service. This vulnerability is fixed by the c43af7806e65adfcf4d0feeebef76dc36c95cb9a and 4b9745fe1a326ce08d69f8a388331bc993d19389 commits.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2025-53532?


## How do I fix CVE-2025-53532?

No fix has been published for CVE-2025-53532 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-53532 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53532 and fix it if it is affected.

What it is: CVE-2025-53532 is a medium-severity missing authorization vulnerability in giscus, published on 7 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53532 in the wild and no public exploit code.

Affected product: giscus. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2025-53532/ (Markdown: https://insights.sbomify.com/CVE-2025-53532/index.md)
```

## Sources

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

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