CVE-2026-55593
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 14% of all known CVEs.
References
Related Vulnerabilities
Other CWE-352 (Cross-Site Request Forgery) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2016-6277 | High | 8.8 | 100% | KEV | - |
| CVE-2022-41622 | High | 8.8 | 92% | - | - |
| CVE-2014-0054 | Medium | 6.8 | 91% | - | Fix |
| CVE-2013-6429 | Medium | 6.8 | 90% | - | Fix |
| CVE-2018-7700 | High | 8.8 | 75% | - | - |
| CVE-2015-2295 | Medium | 6.8 | 66% | - | - |
Common questions
How do I fix CVE-2026-55593?
No published fix for CVE-2026-55593 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-55593 being actively exploited?
Not that we know of. CVE-2026-55593 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.23% is the estimated probability that it will be exploited in the next 30 days. That is higher than 14% of all scored CVEs.
How severe is CVE-2026-55593?
CVE-2026-55593 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-55593
Markdown
[](https://tridentstack.com/cve/CVE-2026-55593)HTML
<a href="https://tridentstack.com/cve/CVE-2026-55593"><img src="https://tridentstack.com/cve/badge/CVE-2026-55593.svg" alt="CVE-2026-55593"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-19.