dbcve.org
Pgadmin 4Application · Pgadmin

CVE-2025-12762

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

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 versions up to 9.9 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 confidence

pgAdmin versions up to 9.9 contain an RCE vulnerability when running in server mode and restoring PLAIN-format PostgreSQL dump files. The restore functionality does not properly sanitize or validate commands embedded in dump files, allowing attackers to inject and execute arbitrary OS commands on the server hosting pgAdmin.

MitigationUpgrade pgAdmin to the patched version (9.10 or later) and avoid restoring untrusted PLAIN-format dump files until the update is applied. Run pgAdmin in server mode only when necessary and with appropriate network access controls.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Identify pgAdmin 4 version
    Check the installed version by reviewing the About dialog in pgAdmin, the version file in the installation directory, or the package manager output if installed via pip (pip show pgadmin4). Compare the version number to the affected range (versions before 9.10).
    Affected if The installed version is pgAdmin 4 version 9.9 or earlier.
  2. Confirm server mode is enabled
    Review the pgAdmin configuration files (config_local.py or config.py) for the ENABLE_SERVER_MODE setting, or check for the presence of the SECRET_KEY configuration option which indicates server mode operation. Alternatively, check if pgAdmin is running as a WSGI/Flask server accessible over HTTP/HTTPS.
    Affected if Server mode is enabled (ENABLE_SERVER_MODE is set to True in the configuration).
  3. Verify restore functionality is accessible
    Check if the pgAdmin web interface includes the 'Restore' option under the database context menu, or verify that the restore endpoint is available in the server configuration. Confirm that untrusted users or public access can initiate restore operations.
    Affected if Restore functionality is enabled and accessible to users who can load untrusted PLAIN-format dump files.
  4. Confirm PLAIN format restore capability
    Verify that pgAdmin supports restoring PLAIN-format PostgreSQL dumps by checking the available format options in the Restore dialog or examining the supported restore formats in the configuration.
    Affected if PLAIN format restore option is available and can be selected by users.

If pgAdmin 4 version 9.9 or earlier is running in server mode with restore functionality enabled and accessible to untrusted users, the environment is affected by this RCE vulnerability.

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 pgAdmin to the patched version (9.10 or later) and avoid restoring untrusted PLAIN-format dump files until the update is applied. Run pgAdmin in server mode only when necessary and with appropriate network access controls.

Recommended fix High confidence

pgAdmin 4 version 9.10 or later

  1. Backup your current pgAdmin 4 configuration and any important data
  2. Stop the pgAdmin 4 server if it is currently running
  3. Upgrade pgAdmin 4 to version 9.10 or later using your installation method (pip, container, or system package manager)
  4. Verify the installed version matches or exceeds 9.10
  5. Restart the pgAdmin 4 server
  6. Confirm the pgAdmin web interface is accessible and functioning normally

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

Fix this in Pgadmin 4 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12762 — 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-12762 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