CVE-2024-32716Network attack vector

Twitch API credential disclosure via client-side requests

Published Apr 24, 2024 · Updated Apr 28, 2026

Sensitive information exposure in StreamWeasels Twitch Integration 1.7.8 and earlier allows remote attackers to read Twitch API credentials. Front-end JavaScript sends Twitch API requests with the configured client ID and OAuth token, exposing both values to site visitors. No authentication or user interaction is required, and the reported impact is limited to disclosure of those API credentials.

CVSS severity5.3
Medium
EPSS probability0.55%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Sensitive information exposure in StreamWeasels Twitch Integration 1.7.8 and earlier allows remote attackers to read Twitch API credentials. Front-end JavaScript sends Twitch API requests with the configured client ID and OAuth token, exposing both values to site visitors. No authentication or user interaction is required, and the reported impact is limited to disclosure of those API credentials.

The record

CVE
CVE-2024-32716
Published
Apr 24, 2024
Updated
Apr 28, 2026
Vendor
StreamWeasels
Product
StreamWeasels Twitch Integration
Classifications
CWE-200, T1552
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 24, 2024CVE publishedPublication date reported by the CVE source.
  2. Apr 28, 2026Record 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.

  1. Affected versionversion=n/a <=1.7.8 changes=[{"at":"1.8.0","status":"unaffected"}]

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

StreamWeasels · StreamWeasels Twitch Integrationversion=n/a <=1.7.8 changes=[{"at":"1.8.0","status":"unaffected"}]
StreamWeasels · Twitch Playerversion=0 <=1.7.8

Published CVSS scores

5.3PatchstackCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1552Unsecured Credentials

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