Security Digest · Vulnerability record
CVE-2024-39907: 1Panel has an SQL injection issue related to the orderBy clause
1Panel is a web-based linux server management control panel.
CVSS 9.3 Critical EPSS 29.2% · p98
Should you act?
High exploit likelihood
EPSS ranks it in the top 5% of all CVEs for likely exploitation in the next 30 days. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 29.2%, percentile 98: FIRST’s model estimates a 29.2% chance of exploitation activity in the next 30 days, higher than 98% of all scored CVEs (very high). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
github.com/1Panel-dev/1Panel(Go) < 1.10.12-tls, fixed in 1.10.12-tls. Check your lockfile, including transitive dependencies.
What it is
1Panel is a web-based linux server management control panel. There are many sql injections in the project, and some of them are not well filtered, leading to arbitrary file writes, and ultimately leading to RCEs. These sql injections have been resolved in version 1.10.12-tls. Users are advised to upgrade. There are no known workarounds for these issues.
From the GitHub advisory
Summary There are many sql injections in the project, and some of them are not well filtered, leading to arbitrary file writes, and ultimately leading to RCEs. The proof is as follows
Details （one of them ）
PoC curl 'http://api:30455/api/v1/hosts/command/search' {"page":1,"pageSize":10,"groupID":0,"orderBy":"3","order":"ascending","name":"a"} for example as picture . just change orderby‘s num we can know How many columns does the data table have.Parameters require strict whitelist filtering
Impact RCE、data leak.
Weakness type: CWE-89.
Product: github.com/1Panel-dev/1Panel (Go) · Assigned by: GitHub_M · Published: 2024-07-18
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| Go | github.com/1Panel-dev/1Panel | < 1.10.12-tls | 1.10.12-tls |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| 1Panel-dev | 1Panel | >= 1.10.9-tls, < 1.10.12-tls |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_M | 3.1 | 9.8 Critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Attack requirements: none
- Privileges required: none (no login)
- User interaction: none
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable yes, technical impact total.
- FIRST EPSS (model of 2026-10-21): 29.18% probability of exploitation activity in the next 30 days; percentile 98.
Timeline
- — CVE record published by GitHub_M
- — GitHub-reviewed advisory GHSA-5grx-v727-qmq6 published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-5grx-v727-qmq6 github.com
- CVE.org record CVE-2024-39907 cve.org
- NVD entry CVE-2024-39907 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com
- github.com github.com