Unauthorized discussion creation via missing token validation
Published Jul 7, 2025 · Updated Jul 7, 2025
Improper authorization in giscus before commit c43af78 allows remote attackers to create discussions in repositories using the service. The POST handler in pages/api/discussions either omits bearer-token validation or fails to await its asynchronous token check before creating a discussion. No authentication or user interaction is required, and the bounded consequence is unauthorized discussion creation rather than a bypass of GitHub content moderation.
Summary
What happened
Improper authorization in giscus before commit c43af78 allows remote attackers to create discussions in repositories using the service. The POST handler in pages/api/discussions either omits bearer-token validation or fails to await its asynchronous token check before creating a discussion. No authentication or user interaction is required, and the bounded consequence is unauthorized discussion creation rather than a bypass of GitHub content moderation.
The record
- CVE
- CVE-2025-53532
- Published
- Jul 7, 2025
- Updated
- Jul 7, 2025
- Vendor
- giscus
- Product
- giscus
- Classifications
- CWE-285, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 7, 2025CVE publishedPublication date reported by the CVE source.
- Jul 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< c43af7806e65adfcf4d0feeebef76dc36c95cb9a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo