VYPR

PyPI package

pgadmin4

pkg:pypi/pgadmin4

Vulnerabilities (20)

  • CVE-2026-1707Feb 5, 2026
    affected < 9.12fixed 9.12

    pgAdmin versions 9.11 are affected by a Restore restriction bypass via key disclosure vulnerability that occurs when running in server mode and performing restores from PLAIN-format dump files. An attacker with access to the pgAdmin web interface can observe an active restore ope

  • CVE-2025-13780Dec 11, 2025
    affected < 9.11fixed 9.11

    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

  • CVE-2025-12765Nov 13, 2025
    affected < 9.10fixed 9.10

    pgAdmin <= 9.9  is affected by a vulnerability in the LDAP authentication mechanism allows bypassing TLS certificate verification.

  • CVE-2025-12764Nov 13, 2025
    affected < 9.10fixed 9.10

    pgAdmin <= 9.9  is affected by an LDAP injection vulnerability in the LDAP authentication flow that allows an attacker to inject special LDAP characters in the username, causing the DC/LDAP server and the client to process an unusual amount of data DOS.

  • CVE-2025-12763Nov 13, 2025
    affected < 9.10fixed 9.10

    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

  • CVE-2025-12762Nov 13, 2025
    affected < 9.10fixed 9.10

    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,

  • CVE-2025-9636Sep 4, 2025
    affected < 9.8fixed 9.8

    pgAdmin <= 9.7 is affected by a Cross-Origin Opener Policy (COOP) vulnerability. This vulnerability allows an attacker to manipulate the OAuth flow, potentially leading to unauthorised account access, account takeover, data breaches, and privilege escalation.

  • CVE-2025-2946Apr 3, 2025
    affected < 9.2fixed 9.2

    pgAdmin <= 9.1 is affected by a security vulnerability with Cross-Site Scripting(XSS). If attackers execute any arbitrary HTML/JavaScript in a user's browser through query result rendering, then HTML/JavaScript runs on the browser.

  • CVE-2025-2945Apr 3, 2025
    affected < 9.2fixed 9.2

    Remote Code Execution security vulnerability in pgAdmin 4 (Query Tool and Cloud Deployment modules). The vulnerability is associated with the 2 POST endpoints; /sqleditor/query_tool/download, where the query_commited parameter and /cloud/deploy endpoint, where the high_availabi

  • CVE-2023-1907Jan 9, 2025
    affected < 7.0fixed 7.0

    A vulnerability was found in pgadmin. Users logging into pgAdmin running in server mode using LDAP authentication may be attached to another user's session if multiple connection attempts occur simultaneously.

  • CVE-2024-9014Sep 23, 2024
    affected < 8.12fixed 8.12

    pgAdmin versions 8.11 and earlier are vulnerable to a security flaw in OAuth2 authentication. This vulnerability allows an attacker to potentially obtain the client ID and secret, leading to unauthorized access to user data.

  • CVE-2024-4216May 2, 2024
    affected < 8.6fixed 8.6

    pgAdmin <= 8.5 is affected by XSS vulnerability in /settings/store API response json payload. This vulnerability allows attackers to execute malicious script at the client end.

  • CVE-2024-4215May 2, 2024
    affected < 8.6fixed 8.6

    pgAdmin <= 8.5 is affected by a multi-factor authentication bypass vulnerability. This vulnerability allows an attacker with knowledge of a legitimate account’s username and password may authenticate to the application and perform sensitive actions within the application, such as

  • CVE-2024-3116Apr 4, 2024
    affected < 8.5fixed 8.5

    pgAdmin <= 8.4 is affected by a Remote Code Execution (RCE) vulnerability through the validate binary path API. This vulnerability allows attackers to execute arbitrary code on the server hosting PGAdmin, posing a severe risk to the database management system's integrity and the

  • CVE-2024-2044Mar 7, 2024
    affected < 8.4fixed 8.4

    pgAdmin <= 8.3 is affected by a path-traversal vulnerability while deserializing users’ sessions in the session handling code. If the server is running on Windows, an unauthenticated attacker can load and deserialize remote pickle objects and gain code execution. If the server is

  • CVE-2023-5002Sep 22, 2023
    affected < 7.7fixed 7.7

    A flaw was found in pgAdmin. This issue occurs when the pgAdmin server HTTP API validates the path a user selects to external PostgreSQL utilities such as pg_dump and pg_restore. Versions of pgAdmin prior to 7.6 failed to properly control the server code executed on this API, all

  • CVE-2023-0241Mar 27, 2023
    affected < 6.19fixed 6.19

    pgAdmin 4 versions prior to v6.19 contains a directory traversal vulnerability. A user of the product may change another user's settings or alter the database.

  • CVE-2023-22298Jan 17, 2023
    affected < 6.14fixed 6.14

    Open redirect vulnerability in pgAdmin 4 versions prior to v6.14 allows a remote unauthenticated attacker to redirect a user to an arbitrary web site and conduct a phishing attack by having a user to access a specially crafted URL.

  • CVE-2022-4223Dec 13, 2022
    affected < 6.17fixed 6.17

    The pgAdmin server includes an HTTP API that is intended to be used to validate the path a user selects to external PostgreSQL utilities such as pg_dump and pg_restore. The utility is executed by the server to determine what PostgreSQL version it is from. Versions of pgAdmin prio

  • CVE-2022-0959Mar 16, 2022
    affected < 6.7fixed 6.7

    A malicious, but authorised and authenticated user can construct an HTTP request using their existing CSRF token and session cookie to manually upload files to any location that the operating system user account under which pgAdmin is running has permission to write.