CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-54348

CVE-2026-54348: Second-Order SQL Injection in Froxlor API Layer

Amit Schendel
Amit Schendel
Senior Security Researcher

Aug 19, 2026·6 min read·50 visits

Executive Summary (TL;DR)

A high-severity second-order SQL injection in Froxlor allows authenticated administrative users to store malicious SQL payloads in admin profiles. When those profiles are queried by specific API actions, the unsanitized payload executes directly against the database, enabling complete database exfiltration. This issue is fully patched in Froxlor version 2.3.8.

An authenticated administrator with privileges to manage admin accounts (such as change_serversettings) can execute arbitrary SQL commands via a second-order SQL injection vulnerability. The flaw resides in Froxlor's administrative API endpoints, specifically during the handling of IP address mapping parameters which are stored as serialized arrays and later interpolated without sanitization into active database queries. This vulnerability allows high-privileged administrative attackers to compromise the database. By injecting a payload into administrative profile metadata, an attacker can extract sensitive credentials, manipulate backend settings, or potentially disrupt database integrity. The vulnerability affects all versions of Froxlor prior to 2.3.8.

Vulnerability Overview

Froxlor is an open-source server administration control panel used to manage hosting environments. It exposes an API layer for administrative operations, including system configuration, database administration, and user management. This wide attack surface relies heavily on role-based access controls to isolate different tiers of administrative users.

This vulnerability, tracked as CVE-2026-54348 and GHSA-w27m-rmmf-g5w4, represents a classic trust-boundary violation. It falls under the class of second-order SQL injection (CWE-89). In this class, user input is initially stored safely in a database, only to be retrieved and executed insecurely in a different context or workflow later on.

The vulnerability allows high-privileged administrative attackers to compromise the database. By injecting a payload into administrative profile metadata, an attacker can extract sensitive credentials, manipulate backend settings, or potentially disrupt database integrity. The vulnerability affects all versions of Froxlor prior to 2.3.8.

Root Cause Analysis

The root cause of this vulnerability lies in the lack of data-type validation and strict boundary separation when processing array parameters. Specifically, the API endpoints Admins.add and Admins.update accept an arbitrary array under the ipaddress parameter. The application attempts to serialize this array into a JSON string using json_encode() and write it to the panel_admins.ip column.

During this initial write operation, the application performs a weak check: is_array($ipaddress) && $ipaddress > 0. In PHP, checking if an array is greater than zero simply verifies that the array has one or more elements. It does not validate or sanitize the types of the elements contained within the array itself. Consequently, arbitrary string inputs (including SQL operators and keywords) are successfully stored in the database as a valid JSON array.

The injection payload becomes active during read operations performed by endpoints such as IpsAndPorts.listing and domain validation logic. The application retrieves the JSON string from the database, decodes it back into a PHP array using json_decode(), and directly concatenates the raw array values into an SQL query's IN clause using the PHP implode() function. Because the values are directly concatenated rather than bound as parameterized variables or cast to integers, the interpreter treats the injected strings as structured SQL commands.

Code Analysis

To analyze the vulnerable implementation, consider how the ipaddress parameter was processed in lib/Froxlor/Api/Commands/Admins.php prior to the patch. The array was encoded directly without ensuring its keys or values were restricted to numeric identifiers:

// Vulnerable code in lib/Froxlor/Api/Commands/Admins.php
'ip' => empty($ipaddress) ? '' : (is_array($ipaddress) && $ipaddress > 0 ? json_encode($ipaddress) : -1)

When reading this data, lib/Froxlor/Api/Commands/IpsAndPorts.php executed the following unsafe dynamic SQL construction:

// Vulnerable query interpolation in lib/Froxlor/Api/Commands/IpsAndPorts.php
if (!empty($this->getUserDetail('ip')) && $this->getUserDetail('ip') != -1) {
    $ip_where = 'WHERE id IN (' . implode(', ', json_decode($this->getUserDetail('ip'), true)) . ')';
    $append_where = true;
}

The patch in commit a1eaca5a1601c8a30e00814a4fc73ad0c185f89e addresses this on both the write and read paths. On the write path, the application now enforces that elements must be numeric using array_filter() and explicitly casts elements to integers with array_map('intval') before serialization:

// Patched code in lib/Froxlor/Api/Commands/Admins.php
if (is_array($ipaddress)) {
    $ipaddress = array_filter($ipaddress, 'is_numeric');
}
// ...
'ip' => empty($ipaddress) ? '' : (is_array($ipaddress) && count($ipaddress) > 0 ? json_encode(array_map('intval', $ipaddress)) : -1)

On the read path, even if legacy unvalidated strings exist in the database, the patch forces integer casting on the array elements before they are concatenated into the SQL statement, neutralizing any dynamic string elements:

// Patched query interpolation in lib/Froxlor/Api/Commands/IpsAndPorts.php
if (!empty($this->getUserDetail('ip')) && $this->getUserDetail('ip') != -1) {
    $ip_ids = array_map('intval', json_decode($this->getUserDetail('ip'), true));
    $ip_where = 'WHERE id IN (' . implode(', ', $ip_ids) . ')';
    $append_where = true;
}

Exploitation Methodology

Exploiting this second-order vulnerability requires a two-step administrative sequence. First, the attacker must have an administrative account with the change_serversettings privilege. The attacker targets the API endpoint Admins.add or Admins.update and supplies a maliciously crafted payload within the ipaddress array parameter.

Instead of passing standard numeric IDs, the attacker sends an array containing a nested SQL syntax breakout. For example, passing the array ["1", "1) UNION SELECT 1,2,3,4,group_concat(loginname, 0x3a, password),6,7,8,9,10 FROM panel_admins -- "] causes the JSON encoder to write the serialized string representation of this structure to the database column panel_admins.ip of the targeted user profile.

In the second stage, the attacker authenticates as the modified user or forces the execution of the listing query by invoking the IpsAndPorts.listing command. When the system executes this API action, it pulls the string from the database, decodes the array, and implodes it into the query. The database engine executes the command, processing the UNION SELECT payload, which allows the attacker to dump password hashes or bypass access controls.

Impact Assessment

The impact of this vulnerability is significant, as it grants complete access to the underlying database structure. An administrative attacker with restricted scope can elevate privileges, bypass regional controls, and extract sensitive information from all tables in the database.

The most critical threat vector is the exposure of administrative user credentials. By executing UNION statements, the attacker can extract user login names and their bcrypt-hashed passwords. Since many administrators reuse passwords across internal systems, this credential theft could lead to further compromise of the hosting infrastructure.

Furthermore, the ability to write to the database or alter system settings via SQL execution compromises the entire hosting panel environment. An attacker could register unauthorized domain records, create administrative backdoors, or tamper with customer configuration files, presenting a high threat to confidentiality, integrity, and availability.

Remediation & Mitigation

The primary remediation for this vulnerability is upgrading Froxlor to version 2.3.8 or higher. The update implements a robust defense-in-depth security model by enforcing structural validations on both the write (input) and read (output) paths.

If patching immediately is not feasible, administrators should audit administrative accounts to ensure that only trusted personnel have the change_serversettings permission. Since the initial injection requires write access to the administrative configuration parameters, limiting this permission minimizes the available attack surface.

Additionally, administrators can execute database-level sanity checks to identify legacy malicious payloads already stored in the database. A query scanning the panel_admins.ip column for non-numeric arrays can pinpoint potential indicator files or compromised configurations before they are triggered by the application logic.

Fix Analysis (1)

Technical Appendix

CVSS Score
7.2/ 10
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected Systems

Froxlor Server Management Control Panel

Affected Versions Detail

Product
Affected Versions
Fixed Version
Froxlor
Froxlor
< 2.3.82.3.8
AttributeDetail
CWE IDCWE-89
Attack VectorNetwork (AV:N)
CVSS v3.17.2 (High)
EPSS ScoreN/A
ImpactHigh (Confidentiality, Integrity, Availability)
Exploit StatusProof of Concept (PoC) documented
KEV StatusNot listed on CISA KEV

MITRE ATT&CK Mapping

T1190Exploit Public-Facing Application
Initial Access
CWE-89
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

The software constructs an SQL command using input from an upstream component, but fails to neutralize elements that could modify the intended SQL command's logic.

Known Exploits & Detection

GitHub Security AdvisoryDetailed explanation of the second-order vulnerability mechanics.

References & Sources

  • [1]GHSA-w27m-rmmf-g5w4: Second-order SQL injection in Froxlor API layer
  • [2]Froxlor Fix Commit a1eaca5a1601c8a30e00814a4fc73ad0c185f89e
  • [3]Froxlor Release 2.3.8
  • [4]NVD - CVE-2026-54348
  • [5]CVE.org Record

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•42 minutes ago•CVE-2026-122247
8.2

CVE-2026-122247: Unauthenticated Global-Admin and Database Creation via Tenant-Confusion Bypass in Budibase

A tenant-confusion vulnerability in the user initialization endpoint of the Budibase worker service (prior to version 3.50.0) allows unauthenticated remote attackers to bypass the one-time administrative setup guard. By supplying arbitrary tenant identifiers in POST requests to /api/global/users/init, an attacker can force the underlying CouchDB datastore to dynamically provision unlimited tenant databases and persist latent global administrator accounts. This results in datastore resource exhaustion, denial of service, and unauthorized administrative account creation inside non-default tenant contexts.

Amit Schendel
Amit Schendel
1 views•9 min read
•about 2 hours ago•CVE-2026-103026
8.1

CVE-2026-103026: Arbitrary Method Invocation and State Tampering in Paymenter via Livewire HasConfirmation Trait

Paymenter versions prior to 1.5.7 contain an arbitrary method invocation vulnerability within the base Livewire component architecture. The application includes a legacy trait, HasConfirmation, inside app/Livewire/Component.php, which is inherited across 36 client-facing Livewire components. This trait exposes a public remote procedure call (RPC) endpoint named executeConfirmedAction without access controls or method allowlisting. Remote attackers can invoke arbitrary methods on any inheriting component, including Livewire's internal fill() method, enabling them to bypass #[Locked] property protections and manipulate internal component state and hydrated Eloquent models.

Alon Barad
Alon Barad
2 views•9 min read
•about 3 hours ago•CVE-2026-104885
6.3

CVE-2026-104885: Cross-Realm MQTT Session Disconnect via Missing Authorization in OpenRemote

OpenRemote prior to version 1.31.0 contains a Missing Authorization vulnerability (CWE-862) in the user management REST API endpoint responsible for disconnecting active MQTT sessions. The disconnectUserSession method in UserResourceImpl fails to verify whether the requesting user owns the target MQTT session, holds administrative privileges, or belongs to the realm specified in the request path. As a result, any authenticated user who obtains a valid MQTT session identifier can forcefully terminate active MQTT connections belonging to other users or IoT devices across any tenant realm.

Amit Schendel
Amit Schendel
2 views•9 min read
•about 4 hours ago•CVE-2026-69133
5.3

CVE-2026-69133: Cumulation Buffer Memory Retention in Netty OHTTP Codec

CVE-2026-69133 (GHSA-cg26-4c6j-2x8h) is a missing resource release vulnerability (CWE-772) in io.netty.incubator:netty-incubator-codec-ohttp affecting versions 0.0.20.Final through 0.0.26.Final. Both OHttpClientCodec and OHttpServerCodec retain the outer cumulationBuffer at its expanded high-water capacity after an Oblivious HTTP (OHTTP) exchange finishes. A remote unauthenticated attacker can complete a large OHTTP request or response over an HTTP keep-alive connection and leave the connection idle, pinning pooled or direct memory allocations across concurrent connections to induce denial of service.

Amit Schendel
Amit Schendel
2 views•8 min read
•about 5 hours ago•CVE-2026-104773
6.8

CVE-2026-104773: Session Fixation in CKAN User Registration View

A session fixation vulnerability (CWE-384) exists in CKAN (Comprehensive Knowledge Archive Network) prior to versions 2.10.11 and 2.11.6. When configured with server-side session storage and active public web registration, the user registration view programmatically authenticates newly created accounts without regenerating the active session identifier. An attacker capable of fixing or capturing a victim's pre-authentication session cookie can hijack the newly registered account immediately after registration completes.

Alon Barad
Alon Barad
2 views•9 min read
•about 6 hours ago•CVE-2026-35374
6.3

CVE-2026-35374: Arbitrary File Truncation via TOCTOU Race Condition in uutils coreutils split

CVE-2026-35374 is a Time-of-Check to Time-of-Use (TOCTOU) race condition (CWE-367) in the split utility of uutils coreutils. The utility validates that the input and output paths do not refer to the same file before opening the output file with truncation flags. A local attacker with write permissions in the destination directory can replace the output file path with a symbolic link during this race window, causing the process to truncate and overwrite arbitrary files accessible to the user executing split.

Amit Schendel
Amit Schendel
2 views•11 min read