dbcve.org
Pgadmin 4Application · Pgadmin

CVE-2025-2946

MEDIUM · 6.1 CVSS v3.1 Published 2025-04-03
Fix available
A fix is available. Upgrade to after 9.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

pgAdmin versions 9.1 and below contain a stored Cross-Site Scripting (XSS) vulnerability in the query result rendering component. Attackers can inject malicious HTML/JavaScript payloads into query results that, when displayed to users, execute in their browsers, potentially stealing session cookies or performing actions on behalf of the victim.

MitigationUpgrade pgAdmin to version 9.2 or later to obtain the security patch. As a temporary measure, disable query result rendering or restrict database access to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pgadmin 4Application
Affected:<= 9.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify pgAdmin 4 installation and version
    Locate the pgAdmin 4 installation and determine its version number. In the pgAdmin web interface, this is typically shown in the Help > About section. If installed as a Python package, run 'pip show pgadmin4' or check the version in the package metadata.
    Affected if The installed version is 9.1 or lower.
  2. Confirm query result rendering is enabled
    Check if the query tool and its result grid feature are enabled in pgAdmin. This is the component that renders SQL query results in the browser. Look for query history or result set display functionality in the configuration.
    Affected if Query result rendering is active and users can execute queries against databases.
  3. Verify database connectivity and query execution access
    Determine if any pgAdmin users have the ability to connect to databases and execute SQL queries. Check for configured database server connections and the presence of the Query Tool in user roles.
    Affected if Users can connect to databases and run SQL queries through pgAdmin.
  4. Compare installed version against affected range
    Review the confirmed pgAdmin 4 version against the affected range of versions 9.1 and below.
    Affected if The version falls within the affected range of 9.1 or below.

A user is affected if they run pgAdmin 4 version 9.1 or lower with query result rendering enabled and have users who can execute database queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 9.1
Interim mitigation

Upgrade pgAdmin to version 9.2 or later to obtain the security patch. As a temporary measure, disable query result rendering or restrict database access to trusted users only.

Recommended fix Moderate confidence

pgAdmin 4 version greater than 9.1 (latest stable release)

  1. 1. Backup your current pgAdmin configuration and database
  2. 2. Download the latest pgAdmin 4 release from the official source (https://www.pgadmin.org/download/)
  3. 3. Stop the pgAdmin service
  4. 4. Install the new version following the installation guide for your operating system
  5. 5. Start the pgAdmin service
  6. 6. Verify the installation by logging in and checking the version number
Caveat Review release notes for any configuration or feature changes between your current version and the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pgadmin 4 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2946 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2946 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data