Pgadmin
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in any Pgadmin product.
Products by Pgadmin Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2025 there have been 2 vulnerabilities in Pgadmin with an average score of 6.6 out of ten. Last year, in 2024 Pgadmin had 1 security vulnerability published. That is, 1 more vulnerability have already been reported in 2025 as compared to last year. Last year, the average CVE base score was greater by 3.20
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2025 | 2 | 6.60 |
| 2024 | 1 | 9.80 |
| 2023 | 3 | 7.13 |
| 2022 | 2 | 7.65 |
| 2021 | 0 | 0.00 |
| 2020 | 0 | 0.00 |
| 2019 | 0 | 0.00 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Pgadmin vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Pgadmin Security Vulnerabilities
pgAdmin <= 9.1 is affected by a security vulnerability with Cross-Site Scripting(XSS)
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.
When batch jobs are executed by pgAgent, a script is created in a temporary directory and then executed
CVE-2025-0218
7.1 - High
- January 07, 2025
When batch jobs are executed by pgAgent, a script is created in a temporary directory and then executed. In versions of pgAgent prior to 4.2.3, an insufficiently seeded random number generator is used when generating the directory name, leading to the possibility for a local attacker to pre-create the directory and thus prevent pgAgent from executing jobs, disrupting scheduled tasks.
Use of Insufficiently Random Values
pgAdmin <= 8.4 is affected by a Remote Code Execution (RCE) vulnerability through the validate binary path API
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.
A flaw was found in pgAdmin
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 versions prior to v6.19 contains a directory traversal vulnerability
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
Open redirect vulnerability in pgAdmin 4 versions prior to v6.14
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
The pgAdmin server includes an HTTP API
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