همهٔ گزارش‌ها
متوسط

Gokapi has stored XSS vulnerability in friendly name for API keys

متن اصلی

نسخه‌های متأثر

بازه‌ها نیاز به بررسی دارند.

نسخه‌های متأثر
< 0.0.0-20250530185940-65ddbc68fbfd
نسخهٔ اصلاح‌شده
0.0.0-20250530185940-65ddbc68fbfd
نسخه‌های متأثر
>= 1.0.1, <= 1.9.6
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
*
نسخهٔ اصلاح‌شده
اعلام نشده

بهره‌برداری

CVE-2025-48495

احتمال بهره‌برداری در ۳۰ روز آینده: 0.14%

FIRST EPSS · ۱۴۰۵/۰۸/۲۸

شرح آسیب‌پذیری

Impact

By renaming the friendly name of an API key, an authenticated user could inject JS into the API key overview, which would also be executed when another user clicks on his API tab. With the affected versions <v2.0, there was no user permission system implemented, therefore all authenticated users were already able to see and modify all resources, even if end-to-end encrypted, as the encryption key had to be the same for all users with <v2.0. Nethertheless with XSS, other attack vectors like redirection or crypto mining would be possble.

Patches

This CVE has been fixed in v2.0.0

Workarounds

If you are the only authenticated user using Gokapi, you are not affected. A workaround would be to not open the API page if you suspect that another user might have injected code.

پیوندها

گزارش‌دهندگان

  • Forceu