CVE-2026-55593Public exploitNetwork attack vectorHinoki check available

API key restriction weakening via CSRF

Published Aug 18, 2026 · Updated Aug 19, 2026

CSRF in Froxlor before 2.3.8 allows remote attackers to weaken API key restrictions via forged administrator requests. The standalone lib/ajax.php entry point bypasses lib/init.php, and Ajax::handle routes state-changing requests after checking only for a valid session; Ajax::editApiKey then updates allowed_from and valid_until without validating a CSRF token. Exploitation requires an administrator to visit an attacker-controlled page while logged in, allowing attackers to add their own source address to an API key or remove its expiration.

CVSS severity6.5
Medium
EPSS probability0.23%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

CSRF in Froxlor before 2.3.8 allows remote attackers to weaken API key restrictions via forged administrator requests. The standalone lib/ajax.php entry point bypasses lib/init.php, and Ajax::handle routes state-changing requests after checking only for a valid session; Ajax::editApiKey then updates allowed_from and valid_until without validating a CSRF token. Exploitation requires an administrator to visit an attacker-controlled page while logged in, allowing attackers to add their own source address to an API key or remove its expiration.

The record

CVE
CVE-2026-55593
Published
Aug 18, 2026
Updated
Aug 19, 2026
Vendor
Froxlor
Product
Froxlor
Classifications
CWE-352
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.3.8

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Froxlor · Froxlorversion=< 2.3.8

Published CVSS scores

6.5GitHub_MCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-352Cross-Site Request Forgery (CSRF)

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo