Skip to main content

pgAdmin 4 CVE-2025-13780

HIGH
Code Injection (CWE-94)
2025-12-11 f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
8.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to server-mode pgAdmin
  2. Delivery
    Upload crafted PLAIN dump file
  3. Exploit
    Trigger restore of malicious dump
  4. Execution
    Inject commands via restore handling
  5. Impact
    Execute arbitrary commands on host

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires pgAdmin 4 running in server (web) mode - not desktop mode - and the attacker (a PR:L authenticated user) must be able to perform a restore operation using a PLAIN-format dump file whose contents they control; the injected commands execute during that restore. Limiting factors: the instance must be deployed in server mode (not every pgAdmin deployment is), the attacker needs a valid account with restore capability, and the malicious PLAIN-format dump must be processed by the restore workflow. These conditions confine realistic exploitation to authenticated or internal users rather than fully anonymous internet attackers.

Impact

This is a genuine high-priority issue, though not a drop-everything emergency. The CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects network-reachable, low-complexity exploitation requiring only low privileges and no user interaction, with full compromise of confidentiality, integrity, and availability - consistent with arbitrary command execution on the host (CWE-94). The signals are, however, not uniformly alarming: EPSS is only 0.94% (60th percentile), indicating modest predicted exploitation likelihood in the near term, and there is no CISA KEV listing and no identified public exploit code, so this is not confirmed active exploitation. The one key tension is PR:L: the vector assumes the attacker already holds a low-privileged pgAdmin account and the ability to run a restore operation, which meaningfully narrows the realistic attacker population to authenticated/internal users or anyone who can obtain valid credentials to a server-mode instance. No SSVC decision data was provided in the input, so automatable/technical-impact framing cannot be independently stated. Net: a legitimately serious authenticated RCE in a DBA tool, warranting prompt patching, but currently lacking evidence of widespread or automated exploitation.

Exploit ScenarioDerived

An authenticated low-privileged user of a server-mode pgAdmin 4 instance (version ≤9.10) supplies a maliciously crafted PLAIN-format PostgreSQL dump file and triggers a restore operation. The restore logic allows injected OS commands to execute on the server hosting pgAdmin, yielding remote code execution in the context of the pgAdmin process. No public proof-of-concept exploit was identified at the time of analysis; the only referenced source is the vendor GitHub issue.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.9% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

Authenticated remote code execution in pgAdmin 4 versions up to and including 9.10 lets a user who holds restore privileges inject and execute arbitrary operating-system commands on the pgAdmin host by submitting a crafted PLAIN-format dump file to the restore workflow while the product runs in server (web) mode. The attacker needs only a valid low-privilege account (CVSS vector PR:L, unauthenticated network reachability of the web interface per AV:N) and no user interaction, giving full compromise of confidentiality, integrity, and availability of the pgAdmin instance and the database credentials and data it manages. Exploitation is gated on a specific deployment posture - server mode rather than desktop mode - and on the ability to trigger a restore of attacker-controlled PLAIN-format input, which confines realistic risk to authenticated or internal users rather than anonymous internet attackers. No public exploit code or CISA KEV entry is associated with this CVE, and EPSS is modest at 0.94% (60th percentile), making this a genuine high-priority issue rather than a drop-everything emergency.

RemediationAI

No exact fixed version is identified in the available data; the only reference is the upstream tracking issue at https://github.com/pgadmin-org/pgadmin4/issues/9368, so the primary action is to monitor that issue and upgrade to the first patched pgAdmin 4 release the project publishes (expected to be later than 9.10). Until a patch is installed, apply compensating controls that match the assessed prerequisites: because exploitation requires server mode plus a restore of attacker-controlled PLAIN-format input, consider restricting the restore capability to trusted administrative roles and auditing which accounts currently hold it - the trade-off is reduced operational flexibility for DBAs. Avoid restoring PLAIN-format dumps from untrusted or externally supplied sources through this instance; require restores of untrusted content to be performed with the PostgreSQL client utilities directly on a hardened host, which removes the pgAdmin command-injection surface but adds manual steps. Where the multi-user web interface is not essential, running pgAdmin in desktop mode eliminates the vulnerable server-mode code path entirely, at the cost of losing centralized, browser-based access. Additionally, run the pgAdmin service under a dedicated low-privilege account, constrain its outbound network access, and isolate it in a container or segmented host so that any successful command execution does not yield lateral reach into the database tier; treat any pgAdmin instance that has already processed untrusted dumps as potentially compromised and rotate stored PostgreSQL credentials.

Affected Packages

pypi pgadmin4 fix: 9.11

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in pypi

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-94 (Improper Control of Generation of Code, i.e. code injection). pgAdmin 4, the popular web-based management client for PostgreSQL, implements its backup/restore feature by shelling out to the PostgreSQL client utilities (pg_restore/psql) on the server hosting the pgAdmin process. When the product is deployed in server (web) mode - the multi-user configuration where pgAdmin runs as a shared service - a restore operation against a PLAIN-format dump causes pgAdmin to process the file's contents through that external command pipeline. Because attacker-controlled content in the dump is not adequately sanitized before being fed into command execution, embedded payloads are interpreted and run with the privileges of the pgAdmin service account. This differs from desktop mode, where the process runs under the local interactive user and the trust boundary is much narrower. The CPE string cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:postgresql:*:*: confirms the affected artifact is the pgAdmin 4 package for the PostgreSQL platform, and the CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates a low-complexity, no-interaction attack that requires only low privileges and yields high impact across all three security objectives within the pgAdmin component's own security scope.

Know when Pgadmin 4 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable server mode (AV:N), low complexity (AC:L), requires an authenticated restore-capable account (PR:L), attacker self-triggers restore so UI:N, and RCE yields full C/I/A on the host.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE 9.1 CRITICAL
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionNVD

pgAdmin versions up to 9.10 are affected by a Remote Code Execution (RCE) vulnerability that occurs when running in server mode and performing restores from PLAIN-format dump files. This issue allows attackers to inject and execute arbitrary commands on the server hosting pgAdmin, posing a critical risk to the integrity and security of the database management system and underlying data.

Executive ViewAI

Why It Matters

pgAdmin 4 deployments running in server (web) mode up to and including 9.10 are exposed to an authenticated remote code execution flaw that can let a low-privilege user with restore rights compromise the pgAdmin host and the database credentials and data it manages. Although no public exploit identified at time of analysis and EPSS is modest, the high severity and potential for full confidentiality, integrity, and availability impact warrant leadership attention because pgAdmin often serves as a privileged gateway to critical database environments. Organizations should prioritize reducing exposure and monitoring until a vendor fix is released.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: run pgAdmin in desktop mode where feasible or restrict server mode to trusted networks; remove restore privileges from low-privilege accounts; disable or tightly control the restore workflow and reject untrusted PLAIN-format dumps; monitor restore activity and host process execution; and apply vendor updates as soon as a fixed pgAdmin release is available.

Threat Intelligence Overview

EPSS Score
0.9%
Top 40% exploitable
Prevalence
Medium
popular PostgreSQL admin tool, but web server-mode deployments less universal
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.9%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Affected Products (CPE)NVD

cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:postgresql:*:*
CVE-2025-2945 CRITICAL POC
9.9 Apr 03

pgAdmin 4 contains critical remote code execution vulnerabilities in the Query Tool download and Cloud Deployment endpoi

CVE-2024-2044 CRITICAL POC
9.9 Mar 07

pgAdmin <= 8.3 is affected by a path-traversal vulnerability while deserializing users’ sessions in the session handling

CVE-2024-3116 CRITICAL POC
9.8 Apr 04

pgAdmin <= 8.4 is affected by a Remote Code Execution (RCE) vulnerability through the validate binary path API. Rated cr

CVE-2022-4223 HIGH POC
8.8 Dec 13

The pgAdmin server includes an HTTP API that is intended to be used to validate the path a user selects to external Post

CVE-2024-9014 MEDIUM POC
6.5 Sep 23

pgAdmin versions 8.11 and earlier are vulnerable to a security flaw in OAuth2 authentication. Rated medium severity (CVS

CVE-2026-12046 CRITICAL
9.5 Jun 18

Remote unauthenticated access to two SQL Editor endpoints in pgAdmin 4 server-mode deployments (versions 6.9 through 9.1

CVE-2026-12045 CRITICAL
9.4 Jun 18

Remote SQL injection via prompt injection in pgAdmin 4 versions 9.13 through 9.15 allows attackers who can write content

CVE-2026-17351 CRITICAL
9.4 Jul 31

SQL injection sandbox escape in pgAdmin 4's AI Assistant (versions 9.13 through 9.16) lets an attacker break out of the

CVE-2026-17566 CRITICAL
9.4 Jul 31

OS command injection in pgAdmin 4 (all versions before 9.18) lets an authenticated user with the commonly-granted tools_

CVE-2026-7813 CRITICAL
9.4 May 11

Authorization bypass and privilege escalation in pgAdmin 4 server mode allows authenticated users to access other users'

CVE-2024-4216 MEDIUM POC
5.4 May 02

pgAdmin <= 8.5 is affected by XSS vulnerability in /settings/store API response json payload. Rated medium severity (CVS

CVE-2026-86863 CRITICAL
9.3 Sep 17

Authentication bypass in pgAdmin 4 (versions 6.2 through 9.17) lets any client that can reach the pgAdmin web interface

Vendor StatusVendor

SUSE

Severity: Critical
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Module for Python 3 15 SP7 Not-Affected
SUSE Linux Enterprise Server 15 SP7 Not-Affected
SUSE Linux Enterprise Server for SAP Applications 15 SP7 Not-Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy