Stored XSS via unsafe API-key name rendering
Published Jun 2, 2025 · Updated Jun 2, 2025
Stored XSS in Gokapi before 2.0.0 allows remote authenticated users to execute JavaScript in another user's browser via a crafted API-key name. The API-key administration script writes the friendly name to table cells with innerHTML, causing stored markup to be parsed; the patch replaces those assignments with innerText. Exploitation requires multiple authenticated users and a victim who opens the attacker's API tab, enabling browser-context actions such as redirection or cryptomining.
Summary
What happened
Stored XSS in Gokapi before 2.0.0 allows remote authenticated users to execute JavaScript in another user's browser via a crafted API-key name. The API-key administration script writes the friendly name to table cells with innerHTML, causing stored markup to be parsed; the patch replaces those assignments with innerText. Exploitation requires multiple authenticated users and a victim who opens the attacker's API tab, enabling browser-context actions such as redirection or cryptomining.
The record
- CVE
- CVE-2025-48495
- Published
- Jun 2, 2025
- Updated
- Jun 2, 2025
- Vendor
- Forceu
- Product
- Gokapi
- Classifications
- CWE-80, CWE-87, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 2, 2025CVE publishedPublication date reported by the CVE source.
- Jun 2, 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=< 2.0.0
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.
Weakness, pattern, technique
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