How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

355,754

Total vulnerabilities in the database

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

Incorrect Authorization

Summary

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.

Details

In lib/Froxlor/Api/Commands/Domains.php, the add() method accepts adminid as an optional parameter at line 327:

$adminid = intval($this-&gt;getParam(&#039;adminid&#039;, true, $this-&gt;getUserDetail(&#039;adminid&#039;)));

The validation for this parameter only runs when the caller has customers_see_all == '1' (lines 410-421):

if ($this-&gt;getUserDetail(&#039;customers_see_all&#039;) == &#039;1&#039; &amp;&amp; $adminid != $this-&gt;getUserDetail(&#039;adminid&#039;)) {
    $admin_stmt = Database::prepare(&quot;
        SELECT * FROM `&quot; . TABLE_PANEL_ADMINS . &quot;`
        WHERE `adminid` = :adminid AND (`domains_used` &lt; `domains` OR `domains` = &#039;-1&#039;)&quot;);
    $admin = Database::pexecute_first($admin_stmt, [
        &#039;adminid&#039; =&gt; $adminid
    ], true, true);
    if (empty($admin)) {
        Response::dynamicError(&quot;Selected admin cannot have any more domains or could not be found&quot;);
    }
    unset($admin);
}

When a reseller does not have customers_see_all (the common case for limited resellers), there is no else branch to force $adminid = $this->getUserDetail('adminid'). The unvalidated $adminid flows directly into:

The domain INSERT at line 757: 'adminid' => $adminid
The quota increment at lines 862-868:

$upd_stmt = Database::prepare(&quot;
    UPDATE `&quot; . TABLE_PANEL_ADMINS . &quot;` SET `domains_used` = `domains_used` + 1
    WHERE `adminid` = :adminid
&quot;);
Database::pexecute($upd_stmt, [&#039;adminid&#039; =&gt; $adminid], true, true);

Compare with Domains.update() at lines 1386-1387 which correctly handles this case:

} else {
    $adminid = $result[&#039;adminid&#039;];
}

The initial quota check at line 321 checks the caller's own quota ($this->getUserDetail('domains_used')), but since the caller's domains_used is never incremented (the wrong admin's counter is incremented instead), this check passes indefinitely.

Note: The getCustomerData() call at line 407 does correctly restrict the customerid to the reseller's own customers (via Customers.get which filters by adminid). However, this does not prevent the adminid field itself from being spoofed.

PoC

# Step 1: Create a domain with the reseller&#039;s API key, specifying a different admin&#039;s ID
curl -s -u RESELLER_API_KEY:RESELLER_API_SECRET -X POST https://froxlor.example/api.php \
  -d &#039;{&quot;command&quot;: &quot;Domains.add&quot;, &quot;params&quot;: {&quot;domain&quot;: &quot;bypass-test-1.com&quot;, &quot;customerid&quot;: 3, &quot;adminid&quot;: 1}}&#039;

# Where:
# - RESELLER_API_KEY:RESELLER_API_SECRET = API credentials for a reseller WITHOUT customers_see_all
# - customerid=3 = one of the reseller&#039;s own customers
# - adminid=1 = the super-admin&#039;s ID (or any other admin&#039;s ID)

# Step 2: Verify the domain was created with adminid=1
# In the database: SELECT adminid, domain FROM panel_domains WHERE domain=&#039;bypass-test-1.com&#039;;
# Expected: adminid=1

# Step 3: Check the reseller&#039;s quota was NOT incremented
# In the database: SELECT adminid, domains_used, domains FROM panel_admins WHERE adminid=&lt;reseller_id&gt;;
# Expected: domains_used unchanged

# Step 4: Check the target admin&#039;s quota WAS incremented
# In the database: SELECT adminid, domains_used, domains FROM panel_admins WHERE adminid=1;
# Expected: domains_used incremented by 1

# Step 5: Repeat with different domain names to demonstrate unlimited creation
curl -s -u RESELLER_API_KEY:RESELLER_API_SECRET -X POST https://froxlor.example/api.php \
  -d &#039;{&quot;command&quot;: &quot;Domains.add&quot;, &quot;params&quot;: {&quot;domain&quot;: &quot;bypass-test-2.com&quot;, &quot;customerid&quot;: 3, &quot;adminid&quot;: 1}}&#039;

curl -s -u RESELLER_API_KEY:RESELLER_API_SECRET -X POST https://froxlor.example/api.php \
  -d &#039;{&quot;command&quot;: &quot;Domains.add&quot;, &quot;params&quot;: {&quot;domain&quot;: &quot;bypass-test-3.com&quot;, &quot;customerid&quot;: 3, &quot;adminid&quot;: 1}}&#039;

# The reseller&#039;s domains_used remains unchanged, allowing indefinite creation

Impact

Quota bypass: A reseller can create unlimited domains beyond their allocated quota, since their own domains_used counter is never incremented.
Quota exhaustion DoS: The target admin's domains_used counter is incremented instead, potentially exhausting their quota and preventing legitimate domain creation.
Data integrity violation: Domains are associated with an admin who does not own the customer, breaking the ownership model. These domains become invisible to the reseller in domain listings (which filter by adminid) but remain active on the server.
Accounting inaccuracy: Resource usage reporting and billing tied to admin quotas becomes incorrect.

Recommended Fix

Add an else branch to force $adminid to the caller's own admin ID when customers_see_all != '1', consistent with the pattern used in Domains.update():

// In lib/Froxlor/Api/Commands/Domains.php, after line 421:

if ($this-&gt;getUserDetail(&#039;customers_see_all&#039;) == &#039;1&#039; &amp;&amp; $adminid != $this-&gt;getUserDetail(&#039;adminid&#039;)) {
    $admin_stmt = Database::prepare(&quot;
        SELECT * FROM `&quot; . TABLE_PANEL_ADMINS . &quot;`
        WHERE `adminid` = :adminid AND (`domains_used` &lt; `domains` OR `domains` = &#039;-1&#039;)&quot;);
    $admin = Database::pexecute_first($admin_stmt, [
        &#039;adminid&#039; =&gt; $adminid
    ], true, true);
    if (empty($admin)) {
        Response::dynamicError(&quot;Selected admin cannot have any more domains or could not be found&quot;);
    }
    unset($admin);
} else {
    // Force adminid to the caller&#039;s own ID when they don&#039;t have customers_see_all
    $adminid = intval($this-&gt;getUserDetail(&#039;adminid&#039;));
}

Published: Apr 16, 2026
Updated: Apr 16, 2026
GHSA: GHSA-jvx4-xv3m-hrj4
Severity: Medium
Exploit:
CISA KEV:

CVSS v3:

Severity: Unknown
Score:
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

CWEs:

CWE-863

Affected Software
References

Software	From	Fixed in
froxlor / froxlor	-	2.3.6

https://github.com/froxlor/froxlor/security/advisories/GHSA-jvx4-xv3m-hrj4

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.