Vulnerabilities

Symbolic-link path traversal (CWE-61, CWE-22) in pgAdmin 4 File Manager.<br /> <br /> check_access_permission used os.path.abspath, which resolves &amp;#39;..&amp;#39; but does not resolve symbolic links, while the subsequent kernel write follows symlinks. An authenticated user could plant a symbolic link inside their own storage directory pointing outside it and induce pgAdmin to write to any path reachable by the pgAdmin process.<br /> <br /> Fix switches the access check to os.path.realpath for both source and destination, and adds an _open_upload_target helper that opens the target with O_NOFOLLOW (mode 0o600) to close the leaf-component TOCTOU between the access check and the open. File mode is hardened from 0o644 to 0o600.<br /> <br /> This issue affects pgAdmin 4: before 9.15.

Improper restriction of excessive authentication attempts (CWE-307) in pgAdmin 4.<br /> <br /> pgAdmin enforces MAX_LOGIN_ATTEMPTS only inside its custom /authenticate/login view. Flask-Security&amp;#39;s default /login view, which is registered automatically by security.init_app() and is reachable on every server, never consulted the User.locked field: pgAdmin&amp;#39;s User model relied on Flask-Security&amp;#39;s UserMixin.is_locked() (which always returns &amp;#39;not locked&amp;#39;) and Flask-Login&amp;#39;s is_active (which only checks the active column, not locked). An attacker who triggered an account lockout via /authenticate/login could therefore obtain a session by re-submitting valid credentials directly to /login, defeating the brute-force-protection control for accounts using the INTERNAL authentication source. The same bypass also means that login attempts via /login are never rate-limited, so an attacker can perform an unbounded online password-guessing attack against INTERNAL accounts regardless of MAX_LOGIN_ATTEMPTS.<br /> <br /> Fix overrides User.is_active and User.is_locked() so the locked column is enforced on every authentication path. LDAP, OAuth2, Kerberos, and Webserver users are not reachable by this bypass because they have no local password and are rejected by Flask-Security&amp;#39;s LoginForm.validate before the locked check; the lockout itself is also internal-only (the /authenticate/login view filters by auth_source=INTERNAL).<br /> <br /> This issue affects pgAdmin 4: before 9.15.

OS command injection (CWE-78) vulnerability in pgAdmin 4 Import/Export query export.<br /> <br /> User-supplied input was interpolated directly into a psql \copy metacommand template without sanitization. An authenticated user could inject ") TO PROGRAM &amp;#39;cmd&amp;#39;" to break out of the \copy (...) context and achieve arbitrary command execution on the pgAdmin server, or ") TO &amp;#39;/path&amp;#39;" for arbitrary file write. Additional fields (format, on_error, log_verbosity) were also raw-interpolated and exploitable.<br /> <br /> Fix adds a parens-balance parser modeled on psql&amp;#39;s strtokx tokenizer, allow-lists format/on_error/log_verbosity, rejects null bytes in the query, and tightens type and gating checks.<br /> <br /> This issue affects pgAdmin 4: before 9.15.

Local file inclusion (LFI) and server-side request forgery (SSRF) vulnerabilities in pgAdmin 4 LLM API configuration endpoints.<br /> <br /> User-supplied api_key_file and api_url preferences were passed to the LLM provider clients without validation. An authenticated user could read arbitrary server-side files by pointing api_key_file at any path readable by the pgAdmin process, or coerce pgAdmin into making requests to internal targets (e.g. cloud metadata services such as 169.254.169.254) by setting api_url, exploiting the chat path and model-list endpoints.<br /> <br /> Fix restricts api_key_file to the user&amp;#39;s private storage (server mode) or home directory (desktop mode), enforces a printable-ASCII key shape and a 1024-byte read cap, and gates api_url against a configurable allow-list (config.ALLOWED_LLM_API_URLS) at every entry point.<br /> <br /> This issue affects pgAdmin 4: before 9.15.

Deserialization of untrusted data (CWE-502) in pgAdmin 4 FileBackedSessionManager.<br /> <br /> The session manager performed unsafe deserialization of session-file contents (using Python&amp;#39;s standard object-serialization module) before performing any HMAC integrity check. Any file dropped into the sessions directory was deserialized unconditionally. An authenticated user with write access to the sessions directory (whether by misconfiguration or in combination with another path-traversal flaw) could plant a crafted serialized payload to achieve operating-system level remote code execution under the pgAdmin process identity.<br /> <br /> Fix prepends a 64-byte hex SHA-256 HMAC over the session body, computed with SECRET_KEY, and verifies it via hmac.compare_digest before any deserialization. The check is raised (rather than asserted) on empty SECRET_KEY so it is not stripped under -O.<br /> <br /> This issue affects pgAdmin 4: before 9.15.

An arbitrary file write vulnerability exists in Casdoor&amp;#39;s Local File System storage provider. Due to insufficient path sanitization, an authenticated attacker with administrative privileges can perform a Path Traversal attack to create or overwrite arbitrary files anywhere on the host filesystem, bypassing the application&amp;#39;s intended storage sandbox.

Authorization vulnerability in pgAdmin 4 server mode affecting Server Groups, Servers, Shared Servers, Background Processes, and Debugger modules.<br /> <br /> Multiple endpoints fetched user-owned objects without filtering by the requesting user&amp;#39;s identity. An authenticated user could access another user&amp;#39;s private servers, server groups, background processes, and debugger function arguments by guessing object IDs.<br /> <br /> Additionally, the Shared Servers feature contained multiple issues including credential leakage (passexec_cmd, passfile, SSL keys), privilege escalation via writable passexec_cmd (a shell command executed when establishing the connection) allowing arbitrary command execution in the owner&amp;#39;s process context, and owner-data corruption via SQLAlchemy session mutations. Several owner-only fields (passexec_cmd, passexec_expiration, db_res, db_res_type) were writable by non-owners through the API, and additional fields (kerberos_conn, tags, post_connection_sql) lacked per-user persistence so non-owner edits mutated the owner&amp;#39;s record.<br /> <br /> Fix centralises access control via a new server_access module, scopes all user-owned models with a UserScopedMixin, returns HTTP 410 from connection_manager when access is denied in server mode, suppresses owner-only fields for non-owners across the merge / API response / ServerManager paths, and adds an explicit owner-only write guard. The remediation landed in two pull requests; both are referenced.<br /> <br /> This issue affects pgAdmin 4: before 9.15.

Stored cross-site scripting (XSS) vulnerability in pgAdmin 4 Browser Tree and Explain Visualizer modules.<br /> <br /> User-controlled PostgreSQL object names (database, schema, table, column, etc.) were assigned to DOM elements via innerHTML, allowing crafted object names containing HTML markup to execute attacker-supplied JavaScript in the browser of any pgAdmin user who navigated to or executed EXPLAIN over the malicious object.<br /> <br /> Fix replaces innerHTML with textContent.<br /> <br /> This issue affects pgAdmin 4: before 9.15.

SQL injection vulnerability in pgAdmin 4 Maintenance Tool.<br /> <br /> Four user-supplied JSON fields (buffer_usage_limit, vacuum_parallel, vacuum_index_cleanup, reindex_tablespace) were concatenated directly into the rendered VACUUM/ANALYZE/REINDEX command and passed to psql --command. An authenticated user with the tools_maintenance permission could break out of the option syntax and execute arbitrary SQL on the connected PostgreSQL server. The injected SQL could in turn invoke COPY ... TO PROGRAM to escalate to operating-system command execution on the database host.<br /> <br /> Fix introduces server-side allow-listing of all four fields and switches reindex_tablespace from manual quoting to the qtIdent filter.<br /> <br /> This issue affects pgAdmin 4: before 9.15.

Angular Expressions provides expressions for the Angular.JS web framework as a standalone module. Prior to 1.5.2, an attacker can write a malicious expression using filters that escapes the sandbox to execute arbitrary code on the system. This vulnerability is fixed in 1.5.2.

Corteza contains a SQL injection vulnerability in its Microsoft SQL Server (MSSQL) backend when filtering Compose records by the meta field.This issue affects corteza: 2024.9.8.

Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user with limited access to pages could copy a page they don&amp;#39;t have access to to an area of the site they do. Once coped, they&amp;#39;d be able to view its contents, and potentially publish it. Permissions were correctly checked for the copy destination, but not for the source page. This vulnerability is fixed in 7.0.7, 7.3.2, and 7.4.