How severe is CVE-2024-39907?

CVE-2024-39907 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-39907?

CVE-2024-39907 affects the following packages: github.com/1Panel-dev/1Panel (Go). Ecosystems affected: Go.

How do I fix CVE-2024-39907?

Update github.com/1Panel-dev/1Panel to 1.10.12-tls or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-39907 is resolved across your whole dependency graph.

How do I detect CVE-2024-39907 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/1Panel-dev/1Panel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2024-39907 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2024-39907?

O3 pinpoints whether CVE-2024-39907 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2024-39907 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2024-39907, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is CVE-2024-39907?

CVE-2024-39907 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2024-39907?

A Nuclei detection template exists for CVE-2024-39907, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2024-39907 published, and has it been updated?

CVE-2024-39907 was published on July 18, 2024 and was last updated on July 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

CRITICAL severity

CVE-2024-39907

CRITICAL

CVE-2024-39907 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in github.com/1Panel-dev/1Panel. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2024-39907 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

a sqlinjection in 1Panel

Also known asGHSA-5grx-v727-qmq6GO-2024-2990

Published

Jul 18, 2024

Updated

Jul 15, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Jul 15, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/1Panel-dev/1Panel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/1Panel-dev/1Panel`	all versions	1.10.12-tls

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

1Panel is a web-based linux server management control panel. There are m…

github.comNVDSep 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/1Panel-dev/1Panel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/1Panel-dev/1Panel to 1.10.12-tls or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-39907 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-39907 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-39907. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-39907 in your dependencies?

O3 detects CVE-2024-39907 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works