dbcve.org
FroxlorApplication

CVE-2026-41228

CRITICAL · 9.9 CVSS v3.1 Published 2026-04-23
Fix available
A fix is available. Upgrade to 2.3.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Froxlor is open source server administration software. Prior to version 2.3.6, the Froxlor API endpoint `Customers.update` (and `Admins.update`) does not validate the `def_language` parameter against the list of available language files. An authenticated customer can set `def_language` to a path traversal payload (e.g., `../../../../../var/customers/webs/customer1/evil`), which is stored in the database. On subsequent requests, `Language::loadLanguage()` constructs a file path using this value and executes it via `require`, achieving arbitrary PHP code execution as the web server user. Version 2.3.6 fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Froxlor prior to 2.3.6 has a path traversal vulnerability in the API endpoints Customers.update and Admins.update where the def_language parameter is not validated against available language files. An authenticated attacker can inject a path traversal payload stored in the database, which Language::loadLanguage() later executes via require(), achieving arbitrary PHP code execution as the web server user.

MitigationUpgrade to Froxlor version 2.3.6 which adds proper validation of the def_language parameter against the whitelist of available language files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FroxlorApplication
Affected:< 2.3.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Froxlor version
    Locate the Froxlor version file (commonly includes/version.php or similar) and read the version number defined there
    Affected if The installed version is below 2.3.6
  2. Identify API users with access to Customers.update or Admins.update
    Review API user accounts and their assigned permissions to determine if any authenticated users have access to the Customers.update or Admins.update API endpoints
    Affected if Authenticated users exist with permissions to call these vulnerable endpoints
  3. Inspect database for suspicious def_language values
    Query the database for any unusual values in fields related to the def_language parameter, looking for path traversal sequences such as ../ or ..\
    Affected if Database contains def_language values with path traversal payloads like ../ or absolute paths to unexpected locations
  4. Check Language::loadLanguage for validation
    Examine the Language::loadLanguage() function in the Froxlor PHP source code to determine whether it validates the def_language parameter against a whitelist of available language files before calling require()
    Affected if The function directly uses require() with the def_language parameter without validating it against a whitelist of legitimate language files

You are affected if your Froxlor installation is version 2.3.5 or lower, authenticated API users can access Customers.update or Admins.update, and the def_language parameter is not validated against a whitelist before being passed to require().

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.3.6 or later
Fixed in 2.3.6
Vendor patch github.com →
Interim mitigation

Upgrade to Froxlor version 2.3.6 which adds proper validation of the def_language parameter against the whitelist of available language files.

Recommended fix High confidence

2.3.6

  1. 1. Backup the current Froxlor installation and database before proceeding with any upgrade.
  2. 2. Download Froxlor version 2.3.6 or later from the official source (e.g., github.com/Froxlor/Froxlor).
  3. 3. Extract the new version files to the web server document root, preserving configuration files.
  4. 4. Run the Froxlor update script or navigate to the admin panel to complete the database migration if required.
  5. 5. Verify the upgrade was successful by logging into the Froxlor admin panel.
  6. 6. Test that the `def_language` parameter is now properly validated against the list of available language files.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Froxlor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41228 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41228 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data