CVE-2026-41233 | Froxlor up to 2.3.5 Domains.add adminid authorization
VulDBArchived Apr 23, 2026✓ Full text saved
A vulnerability categorized as problematic has been discovered in Froxlor up to 2.3.5 . This affects the function Domains.add . Such manipulation of the argument adminid leads to incorrect authorization. This vulnerability is listed as CVE-2026-41233 . The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-359109 · CVE-2026-41233 · GCVE-0-2026-41233
FROXLOR UP TO 2.3.5 DOMAINS.ADD ADMINID AUTHORIZATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.3 $0-$5k 1.89+
Summaryinfo
A vulnerability identified as problematic has been detected in Froxlor up to 2.3.5. This vulnerability affects the function Domains.add. Performing a manipulation of the argument adminid results in authorization. This vulnerability is cataloged as CVE-2026-41233. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Detailsinfo
A vulnerability classified as problematic has been found in Froxlor up to 2.3.5. This affects the function Domains.add. The manipulation of the argument adminid with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. This is going to have an impact on integrity, and availability. The summary by CVE is:
Froxlor is open source server administration software. Prior to version 2.3.6, in `Domains.add()`, the `adminid` parameter is accepted from user input and used without validation when the calling reseller does not have the `customers_see_all` permission. This allows a reseller to attribute newly created domains to any other admin, bypassing their own domain quota (since the wrong admin's `domains_used` counter is incremented) and potentially exhausting another admin's quota. Version 2.3.6 fixes the issue.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-41233 since 04/18/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available.
Upgrading to version 2.3.6 eliminates this vulnerability.
Productinfo
Name
Froxlor
Version
2.3.0
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
License
open-source
Website
Product: https://github.com/froxlor/froxlor/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector (GitHub_M): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Authorization
CWE: CWE-863 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: Froxlor 2.3.6
Timelineinfo
04/18/2026 CVE reserved
04/23/2026 +5 days Advisory disclosed
04/23/2026 +0 days VulDB entry created
04/23/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-41233 (🔒)
GCVE (CVE): GCVE-0-2026-41233
GCVE (VulDB): GCVE-100-359109
Entryinfo
Created: 04/23/2026 07:19
Changes: 04/23/2026 07:19 (63)
Complete: 🔍
Cache ID: 99:9AF:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸