212 matches found
CVE-2024-3116_RCE_in_pgadmin_8.4
CVE-2024-3116RCEinpgadmin8.4 Making a lab and testing the CVE-2024-3116, a Remote Code Execution in pgadmin 8.4 pip download .whl file 8. Install pgadmin4 : python -m pip install C:\Users\User\Downloads\pgadmin4-8.4-py3-none-any.whl Folder of installation :...
CVE-2024-9014
This post is a research article published by EQSTLab. CVE-2024-9014 ★ CVE-2024-9014 Sensitive Information Exposure PoC ★ Description CVE-2024-9014 : pgAdmin4 Sensitive Information Exposure description: pgAdmin versions 8.11 and earlier are vulnerable to a security flaw in OAuth2 authentication...
pgAdmin 4 - Authentication Bypass
pgAdmin 4 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. id: CVE-2024-9014 info: name: pgAdmin 4 - Authentication Bypass author...
CVE-2024-9014
CVE-2024-9014 - pgAdmin 4 OAuth2 Authentication Bypass Exploit Tools This repository contains tools to check for and exploit the CVE-2024-9014 vulnerability in pgAdmin 4. The vulnerability allows an attacker to bypass OAuth2 authentication and access sensitive resources. Tools 1...
pgadmin-ai-assistant-sql-injection-cve-2026-17351-lexer-differential-bypass
CVE-2026-17351 — pgAdmin 4 AI 어시스턴트의 렉서 차이를 통한 읽기 전용 우회 CVE-2026-17351에 대한 PoC로, pgAdmin 4의 AI 어시스턴트에서 발생하는 치명적CVSS 9.0 SQL 인젝션 우회입니다. 취약점 요약 pgAdmin 4 버전 9.139.16은 Python sqlparse 라이브러리를 사용하여 LLM이 생성한 SQL 쿼리가 단일 읽기 전용 문장인지 검증합니다. PostgreSQL의 standardconformingstrings = onPostgreSQL 9.1 이후 기본값에서는...
CVE-2025-13780
CVE-2025-13780: pgAdmin 4 = 8.14 RCE Scanner A comprehensive vulnerability scanner for CVE-2025-13780 , a Remote Code Execution RCE vulnerability in pgAdmin 4 versions ≤ 8.14. 🔍 Vulnerability Details The vulnerability exists in the Restore feature of pgAdmin 4. The application attempts to block...
CVE-2025-2945-pgAdmin-RCE
CVE-2025-2945 — pgAdmin 4 認証済みクエリツール RCE CVSS 3.1: 9.9(Critical) · 影響を受けるバージョン: pgAdmin 4 8.10 – 9.1 · 修正バージョン: 9.2(2025年4月4日) CWE-95 (動的評価コードにおけるディレクティブの不適切な無害化 / Eval インジェクション) CVE-2025-2945 の概念実証エクスプロイトです。pgAdmin 4 のクエリツールにおける認証済みリモートコード実行の脆弱性です。ブール型のトランザクション状態フラグ(querycommited)がブール値として解析される代わ...
CVE-2026-17566
CVE-2026-17566 — pgAdmin 4 Import/Export Data RCE PoC PoC de ejecución remota de código en la herramienta Import/Export Data de pgAdmin 4. Aprovecha la divergencia semántica del escape de barra invertida entre el verificador de paréntesis isqueryparensbalanced y psql para inyectar \copy ... TO...
Blackash-CVE-2025-12762
🔐 CVE-2025-12762 — Critical RCE Vulnerability in pgAdmin 4 🚨 What’s the Issue? A Remote Code Execution RCE flaw exists in pgAdmin 4 versions ≤ 9.9. Attackers can run arbitrary commands on the host when pgAdmin is running in server mode and processes a PLAIN-format SQL dump during restore. ⚙️...
pgadmin4-9.10-CVE-2025-13780
pgadmin4 9.11 Meta-Command Filter Command Execution Summary The PLAIN restore meta-command filter introduced in pgAdmin as part of the fix for Issue 9320 does not detect meta-commands when a SQL file begins with a UTF-8 Byte Order Mark EF BB BF or other special sequences. The implemented filter...
CVE-2025-2945-pgadmin-rce
CVE-2025-2945 — pgAdmin 4 Query Tool Authenticated RCE Proof of concept for CVE-2025-2945, a critical remote code execution vulnerability in pgAdmin 4. Affected versions: 8.10 through 9.1 Fixed in: 9.2 released April 4, 2025 CVSS v3.1: 9.9 Critical Overview The pgAdmin 4 Query Tool exposes an...
CVE-2024-2044
PoC CVE-2024-2044: pgAdmin 4 認証済みRCE Linux/POSIX このリポジトリには、Linux/POSIX環境で動作するpgAdmin 4バージョン8.3以下における、認証済みパストラバーサル と安全でないデシリアライゼーション を組み合わせた重大な脆弱性であるCVE-2024-2044 の Proof of ConceptPoCスクリプトが含まれています。 !WARNING 免責事項: このコードは、教育、セキュリティ研究、および正式なペネトレーションテストauthorized...
CVE-2026-86861
A flaw was found in pgAdmin 4. The File Manager's savefile endpoint, used for saving files from the Query Tool and ERD, did not properly handle symbolic links. An authenticated user with existing filesystem access to the pgAdmin host or a shared storage backend could exploit a timing window to...
CVE-2026-86862
A flaw was found in pgAdmin 4. Authenticated users with toolsrestore or toolsmaintenance permissions can exploit a connection-string injection issue in the Restore and Maintenance tools. By manipulating the 'database' field passed to the --dbname option of pgrestore and psql, an attacker can...
CVE-2026-86863
A flaw was found in pgAdmin 4. When the 'webserver' authentication source is enabled, a remote attacker can bypass authentication by supplying a client-controlled identity header. This allows the attacker to authenticate as any user, including an Administrator, without providing valid credentials...
CVE-2026-86864
A flaw was found in pgAdmin 4. An authenticated user with 'toolsbackup' permission can exploit an argument injection vulnerability in the Backup tool to create or overwrite arbitrary files on the system where pgAdmin is running. Additionally, a connection-string injection vulnerability allows the...
CVE-2026-86864
pgAdmin 4's Backup tool appended the client-supplied 'database' field from the /backup/job//object request to the pgdump argument vector as a bare trailing positional argument, without validation. Because pgdump parses its options with getoptlong, which permutes arguments, a value beginning with ...
CVE-2026-86863
pgAdmin 4's Webserver authentication source is intended to accept an identity asserted by the web server or reverse proxy in front of pgAdmin, delivered through the WSGI/CGI environment. WebserverAuthentication.getuser read config.WEBSERVERREMOTEUSER from request.environ and, when that returned...
CVE-2026-86862
pgAdmin 4's Restore and Maintenance tools passed the client-supplied 'database' field directly as the value of the --dbname option given to pgrestore and psql. libpq expands a database name containing an equals sign into a full connection string, and connection keywords embedded in that value tak...
CVE-2026-86864 pgAdmin 4: Argument and connection-string injection via the database field in the Backup tool
pgAdmin 4's Backup tool appended the client-supplied 'database' field from the /backup/job//object request to the pgdump argument vector as a bare trailing positional argument, without validation. Because pgdump parses its options with getoptlong, which permutes arguments, a value beginning with ...