CVE-2026-55593
Froxlor is open source server administration software. Prior to …
Froxlor is open source server administration software. Prior to 2.3.8, the standalone lib/ajax.php entry point bypasses the centralized request validation in lib/init.php, and Ajax::handle in lib/Froxlor/Ajax/Ajax.php checks only for a valid session before routing state-changing requests. The editapikey action in Ajax::editApiKey updates allowed_from and valid_until without validating a CSRF token, while templates/Froxlor/assets/js/jquery/apikeys.js sends no token because the endpoint does not require one. An unauthenticated attacker can induce an authenticated administrator's browser to submit a forged request that adds an attacker-controlled address to an API key's allowed_from list or removes its expiration, weakening the key's security restrictions. This issue is fixed in version 2.3.8.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/froxlor/froxlor/commit/5f540fe361e7e13e8c5a32805b793a25e9e26a0e
- github.com/froxlor/froxlor/releases/tag/2.3.8
- github.com/froxlor/froxlor/security/advisories/GHSA-xpr4-8vp6-c87j
- github.com/advisories/GHSA-xpr4-8vp6-c87j
- nvd.nist.gov/vuln/detail/CVE-2026-55593
- cve.org/CVERecord?id=CVE-2026-55593
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.