Vulnerability Description
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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/froxlor/froxlor/commit/5f540fe361e7e13e8c5a32805b793a25e9e26a
- https://github.com/froxlor/froxlor/releases/tag/2.3.8
- https://github.com/froxlor/froxlor/security/advisories/GHSA-xpr4-8vp6-c87j
FAQ
What is CVE-2026-55593?
CVE-2026-55593 is a vulnerability with a CVSS score of 6.5 (MEDIUM). 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/Frox...
How severe is CVE-2026-55593?
CVE-2026-55593 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-55593?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.