CVE-2026-78387: RansomLook Missing Authorization in Web Configuration Editor Allows Application Configuration Modification
RansomLook contains an authorization weakness in the web-based configuration editor exposed through the /admin/config endpoint. The endpoint requires an authenticated session but does not perform an explicit privilege or administrator authorization check before allowing access to configuration-management functionality.
An authenticated low-privileged user able to access the endpoint can submit crafted configuration values that are written directly to the application's config/generic.json file. The affected functionality permits modification of configuration sections including notification, LDAP, SMTP, and general application settings. Successful exploitation could therefore allow an attacker to alter security-sensitive application behavior, redirect integrations or notifications, modify authentication-related configuration, disrupt external services, or render the RansomLook installation unavailable.
The configuration editor also operated on a configuration file containing sensitive values such as passwords, tokens, secrets, and API keys. Although the affected version contains logic intended to prevent recognized secret values from being returned to the browser, exposing configuration management through insufficiently authorized web functionality significantly increases the impact of a compromised or low-privileged account.
The patch resolves the issue by completely removing the /admin/config route and associated configuration-editing interface, preventing application configuration from being modified through the web UI.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
RansomLook /admin/config web configuration editor route (configuration-editing interface)from your environment.Completely remove the /admin/config route and its associated configuration-editing interface so that application configuration cannot be modified via the web UI.
Event History
Frequently Asked Questions
What level of access does an attacker need to exploit this issue?
The attacker needs an authenticated RansomLook session and the ability to access the /admin/config endpoint. A low-privileged authenticated user may be able to exploit it because the endpoint does not explicitly check for administrator or other elevated privileges.
What can an attacker change through the affected functionality?
An attacker can submit crafted values that are written to config/generic.json. The exposed editor can modify notification, LDAP, SMTP, and general application settings, potentially changing authentication-related behavior, redirecting integrations or notifications, disrupting external services, or making the installation unavailable.