CSRF in Froxlor
CVE-2026-55593
- CVSS v3
- 6.5 Medium
- Public exploits
- None known
- EPSS
- 0.003 · 17.6th percentile
- Published
- 2026-08-18
What to do
- Fixed in
2.3.8- Affected
- 1 affected product
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.
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- Required
UI:R - Scope
- Unchanged
S:U - Confidentiality
- None
C:N - Integrity
- High
I:H - Availability
- None
A:N
EPSS exploit prediction
EPSS 0.003, 17.6th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Froxlor — versions < 2.3.8