pgadmin4 has a Meta-Command Filter Command Execution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L

EPSS

• CVE-2025-13780: 0.94% estimated exploitation activity in the next 30 days; percentile 61.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The PLAIN restore meta-command filter introduced in pgAdmin as part of the fix for CVE-2025-12762 does not detect meta-commands when a SQL file begins with a UTF-8 Byte Order Mark (EF BB BF) or other special byte sequences. The implemented filter uses the function hasmetacommands(), which scans raw bytes using a regular expression. The regex does not treat the bytes as ignorable, so meta-commands such as \\! remain undetected. When pgAdmin invokes psql with --file, psql strips the bytes and executes the command. This can result in remote command execution during a restore operation.

Published by the source

11 Dec 2025, 21:31 UTC

Last modified by the source

29 Jun 2026, 12:26 UTC

Source last checked

26 Oct 2026, 13:36 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-fxmw-jcgr-w44v

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-fxmw-jcgr-w44v

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-fxmw-jcgr-w44v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-13780

Advisory: pgadmin4 has a Meta-Command Filter Command Execution
IDs: CVE-2025-13780, GHSA-fxmw-jcgr-w44v
Record: https://patchnext.com/advisories/cve-2025-13780 (revision 3, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pgadmin4 9.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pgadmin4: affected < 9.11; fixed in 9.11

## Suggested inspection (read-only)
- `python -m pip show pgadmin4`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pgadmin4.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fxmw-jcgr-w44v (GitHub-reviewed advisory GHSA-fxmw-jcgr-w44v lists affected ranges: PyPI pgadmin4 >=0 <9.11)
- Verified: https://osv.dev/vulnerability/GHSA-fxmw-jcgr-w44v (OSV record GHSA-fxmw-jcgr-w44v lists affected ranges: PyPI pgadmin4 >=0 <9.11 (fixed))

Commands are suggestions: review each one before running it.