dbcve.org
Pgadmin 4Application · Pgadmin

CVE-2025-12763

HIGH · 8.8 CVSS v3.1 Published 2025-11-13
Fix available
A fix is available. Upgrade to 9.10 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
pgAdmin 4 versions up to 9.9 are affected by a command injection vulnerability on Windows systems. This issue is caused by the use of shell=True during backup and restore operations, enabling attackers to execute arbitrary system commands by providing specially crafted file path input.

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 confidence

pgAdmin 4 versions up to 9.9 contain a command injection vulnerability on Windows systems where the application uses shell=True in subprocess calls during backup and restore operations. Attackers can execute arbitrary system commands by providing specially crafted file path input.

MitigationUpgrade to a patched version of pgAdmin 4 (beyond 9.9) and implement proper input validation for file paths to prevent injection attacks.

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
Affected:< 9.10

CVSS 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify pgAdmin 4 installation and version
    Check for pgAdmin 4 installation directory (typically C:\Program Files\pgAdmin 4\ or C:\Users\<user>\AppData\Local\Programs\pgAdmin 4\) and locate the version file (version.py or similar) or check the About dialog in the application
    Affected if pgAdmin 4 version is found to be 9.9 or lower (< 9.10)
  2. Confirm operating system is Windows
    Run 'systeminfo' or check OS name from 'winver' command output - the vulnerability specifically affects Windows systems
    Affected if The system is running Windows and pgAdmin 4 is installed
  3. Check if backup/restore feature is accessible
    In pgAdmin 4, navigate to the object browser, right-click on any database, and verify if 'Backup...' or 'Restore...' context menu options are present and functional
    Affected if Backup/restore functionality is enabled and accessible to users
  4. Examine subprocess calls in backup/restore modules
    Locate backup.py and restore.py files in pgAdmin 4 installation (typically under runtime\python\lib\ or similar path) and inspect for subprocess.Popen calls using shell=True parameter during file path handling
    Affected if Code contains subprocess calls with shell=True while handling file paths for backup/restore operations

You are affected if pgAdmin 4 version is below 9.10, running on Windows, and the backup/restore feature is accessible with vulnerable subprocess calls using shell=True present in the code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 9.10 or later
Fixed in 9.10
Interim mitigation

Upgrade to a patched version of pgAdmin 4 (beyond 9.9) and implement proper input validation for file paths to prevent injection attacks.

Recommended fix High confidence

pgAdmin 4 version 9.10

  1. 1. Back up your current pgAdmin 4 configuration and any custom settings
  2. 2. Download pgAdmin 4 version 9.10 or later from the official source (https://www.pgadmin.org/download/)
  3. 3. Install the new version following the standard installation process for your operating system
  4. 4. Verify the installation was successful by checking the pgAdmin 4 version
  5. 5. Test backup and restore functionality to ensure operations work correctly with the patched version
Caveat Minor release; standard security update with no expected breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pgadmin 4 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12763 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12763 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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