Pgadmin 4Application · Pgadmin
CVE-2025-13780
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedpgAdmin 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencepgAdmin versions up to 9.10 contain a Remote Code Execution vulnerability in the database restore functionality. When running in server mode, restoring from PLAIN-format dump files allows attackers to inject arbitrary commands through specially crafted dump content, which are then executed with the privileges of the pgAdmin server process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Pgadmin 4Application
<= 9.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify pgAdmin 4 versionRun 'pip show pgadmin4' or check the About dialog in pgAdmin to find the installed version numberAffected if Installed version is 9.10 or lower
-
Confirm pgAdmin is running in server modeCheck if pgAdmin is accessed via a web browser (typically http://localhost:5050 or similar) rather than as a desktop application. In server mode, pgAdmin runs as a Python Flask application behind a web serverAffected if pgAdmin is accessible as a web application (server mode) rather than desktop mode - server mode is required for remote exploitation
-
Verify PLAIN-format dump restore is accessibleIn pgAdmin server mode, navigate to the 'Restore' dialog (typically under a database node in the Object browser). PLAIN format restore is available in the format dropdown during restore operationsAffected if Users with access to the pgAdmin server can restore PLAIN-format dumps - this feature is present in normal pgAdmin installations
-
Assess access control on restore functionalityReview user accounts and roles in pgAdmin server mode (menu: Tools > User Management) to determine if untrusted users have access to the restore featureAffected if Untrusted or non-admin users have access to the pgAdmin server and can perform restore operations - exploitation requires a user to restore a malicious dump file
A user is affected if they run pgAdmin 4 version 9.10 or lower in server mode with restore functionality accessible to users who might load untrusted PLAIN-format PostgreSQL dump files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade pgAdmin to a version beyond 9.10 when available. Alternatively, avoid restoring PLAIN-format dumps from untrusted sources and restrict pgAdmin server mode access to trusted users only.
Fix this in Pgadmin 4
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13780 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13780 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data