Pgadmin 4
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Pgadmin 4.
By the Year
In 2026 there have been 0 vulnerabilities in Pgadmin 4. Last year, in 2025 Pgadmin 4 had 1 security vulnerability published. Right now, Pgadmin 4 is on track to have less security vulnerabilities in 2026 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 1 | 6.10 |
| 2024 | 1 | 9.80 |
| 2023 | 3 | 7.13 |
| 2022 | 2 | 7.65 |
It may take a day or so for new Pgadmin 4 vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Pgadmin 4 Security Vulnerabilities
pgAdmin <=9.1 XSS via Query Result Rendering
CVE-2025-2946
6.1 - Medium
- April 03, 2025
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.
RCE via validate binary path API in pgAdmin <=8.4
CVE-2024-3116
9.8 - Critical
- April 04, 2024
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 security of the underlying data.
pgAdmin Arbitrary Command Execution via HTTP API path validation flaw before 7.6
CVE-2023-5002
8.8 - High
- September 22, 2023
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, allowing an authenticated user to run arbitrary commands on the server.
pgAdmin 4 <v6.19 DTR: Alter User Settings & DB
CVE-2023-0241
6.5 - Medium
- March 27, 2023
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.
Directory traversal
pgAdmin 4 v<6.14 Open Redirect CVE-2023-22298
CVE-2023-22298
6.1 - Medium
- January 17, 2023
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.
Open Redirect
Unauthenticated API Hijack in pgAdmin <6.17 via Path Execution
CVE-2022-4223
8.8 - High
- December 13, 2022
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 prior to 6.17 failed to properly secure this API, which could allow an unauthenticated user to call it with a path of their choosing, such as a UNC path to a server they control on a Windows machine. This would cause an appropriately named executable in the target path to be executed by the pgAdmin server.
AuthZ
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
CVE-2022-0959
6.5 - Medium
- March 16, 2022
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.
Directory traversal
