Most severe vulnerabilities for "npm/wlc"

Where

Sort:

npm/wlcwlc may leak API keys due to an insecure API key configuration

Risk 24

Severity

5.5

EPSS

0.01%

Infoleak

AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N

Impact Historically, wlc supported providing unscoped API keys in the setting. This practice was discouraged for years, but the code was never removed. This might cause the API key to be used against different server.

Patches https://github.com/WeblateOrg/wlc/pull/1098

Workarounds Remove unscoped key from wlc configuration. Only use URL-scoped keys in the [keys] sections.

References This issue was reported to us by wh1zee via HackerOne.

1 / 2

Source: GitHub

First published (updated )

CVE-2026-22251

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Trending

npm/wlcwlc may leak API keys due to an insecure API key configuration

Company

Resources

Contact