Cyber Resilience

CVE-2024-3116

Command Injection in Pgadmin 4 ≤ 8.4

Public PoCHigh EPSSCommand Injection
Published
04 April 2024
Modified
17 June 2026
CVSS Score v3.1 7.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
EPSS Score 0.65 99.2th percentile
Risk Priority 79 floored blend · peak EPSS

Summary

CVE-2024-3116 is a high-severity Command Injection (CWE-77) vulnerability in Pgadmin Pgadmin 4. Its CVSS base score is 7.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 0.8% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

pgAdmin versions 8.4 and earlier contain a remote code execution vulnerability in the validate binary path API. The flaw, tracked as CVE-2024-3116, carries a CVSS 3.1 score of 7.4 and is associated with CWE-77 command injection, allowing an authenticated user to supply crafted input that results in arbitrary code execution on the host running pgAdmin.

An attacker with low-privileged network access and no user interaction can invoke the affected API endpoint to run commands on the server. Successful exploitation yields limited impact on confidentiality, integrity, and availability while changing scope to other components on the same host, thereby threatening both the pgAdmin instance and any connected PostgreSQL data.

The EPSS score for this CVE stands at 0.9068 with no material increase after disclosure. Public references include a GitHub issue and proof-of-concept material, but no details on official patches or mitigation steps are provided in the available information.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

pgAdmin <= 8.4 is affected by a Remote Code Execution (RCE) vulnerability through the validate binary path API. This vulnerability allows attackers to execute arbitrary code on the server hosting PGAdmin, posing a severe risk to the database management system's…

more

integrity and the security of the underlying data.

CWE(s)
NVD-CWE-noinfoCWE-77

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
attack.mitre.org →
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
attack.mitre.org →
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
attack.mitre.org →
T1059.008 Network Device CLI Execution
Adversaries may abuse scripting or built-in command line interpreters (CLI) on network devices to execute malicious command and payloads.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-5002Same product: Fedoraproject Fedora
CVE-2022-4223Same product: Fedoraproject Fedora
CVE-2024-2044Same product: Fedoraproject Fedora
CVE-2024-4215Same product: Fedoraproject Fedora
CVE-2024-4216Same product: Fedoraproject Fedora
CVE-2023-22298Same product: Fedoraproject Fedora
CVE-2024-25082Same product: Fedoraproject Fedora
CVE-2024-25081Same product: Fedoraproject Fedora
CVE-2023-34153Same product: Fedoraproject Fedora
CVE-2026-12045Same product: Pgadmin Pgadmin 4

Affected Assets

pgadmin
pgadmin 4
≤ 8.4
fedoraproject
fedora
39

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.3
  • V1.2.5
  • V1.2.8
  • V1.2.9

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover command-construction flaws before deployment.

SI-10 Information Input Validation good match

Input validation directly stops construction of commands from untrusted data containing special elements.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles include proper neutralization and safe command construction practices.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and neutralization that prevent command injection.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data can detect anomalous command execution resulting from injection.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding mostly match
prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches command-injection vulnerabilities before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection flaws including command injection.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.

A.8.31 Separation of development, test and production environments none match
none

Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.

References