Froxlor has a Reseller Domain Quota Bypass via Unvalidated adminid Parameter in Domains.add()

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

EPSS

• CVE-2026-41233: 0.26% estimated exploitation activity in the next 30 days; percentile 18.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary In Domains.add(), the adminid parameter is accepted from user input and used without validation when the calling reseller does not have the customersseeall permission. This allows a reseller to attribute newly created domains to any other admin, bypassing their own domain quota (since the wrong admin's domainsused counter is incremented) and potentially exhausting another admin's quota. Details In lib/Froxlor/Api/Commands/Domains.php, the add() method accepts adminid as an optional parameter at line 327: The validation for this parameter only runs when the caller has customersseeall == '1' (lines 410-421): When a reseller does not have customersseeall (the common case for limited resellers), there is no else branch to force $adminid = $this-getUserDetail('adminid'). The unvalidated $adminid flows directly into: 1. The domain INSERT at line 757: 'adminid' = $adminid 2. The quota increment at lines 862-868: Compare with Domains.update() at lines 1386-1387 which correctly…

Published by the source

16 Apr 2026, 00:46 UTC

Last modified by the source

24 Apr 2026, 20:54 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jvx4-xv3m-hrj4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41233

Advisory: Froxlor has a Reseller Domain Quota Bypass via Unvalidated adminid Parameter in Domains.add()
IDs: CVE-2026-41233, GHSA-jvx4-xv3m-hrj4
Record: https://patchnext.com/advisories/cve-2026-41233 (revision 1, source checked 26 Oct 2026, 14:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: froxlor/froxlor 2.3.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist froxlor/froxlor: affected <= 2.3.5; fixed in 2.3.6

## Suggested inspection (read-only)
- Packagist froxlor/froxlor: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on froxlor/froxlor.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jvx4-xv3m-hrj4 (GitHub-reviewed advisory GHSA-jvx4-xv3m-hrj4 lists affected ranges: Packagist froxlor/froxlor >=0 <=2.3.5)

Commands are suggestions: review each one before running it.