dbcve.org
PhppgadminApplication · Phppgadmin Project

CVE-2025-60796

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-20
Fix available
A fix is available. Upgrade to after 7.13.0 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
phpPgAdmin 7.13.0 and earlier contains multiple cross-site scripting (XSS) vulnerabilities across various components. User-supplied input from $_REQUEST parameters is reflected in HTML output without proper encoding or sanitization in multiple locations including sequences.php, indexes.php, admin.php, and other unspecified files. An attacker can exploit these vulnerabilities to execute arbitrary JavaScript in victims' browsers, potentially leading to session hijacking, credential theft, or other malicious actions.

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

Multiple reflected XSS vulnerabilities exist in phpPgAdmin 7.13.0 and earlier where user-supplied input from $_REQUEST parameters is directly reflected in HTML output without sanitization or encoding. Affected files include sequences.php, indexes.php, admin.php, and other unspecified files, allowing attackers to inject arbitrary JavaScript that executes in victim browsers.

MitigationImplement proper input validation and output encoding for all user-supplied data before rendering in HTML. Apply context-appropriate escaping functions (such as htmlspecialchars()) to all $_REQUEST parameters in the affected files and conduct thorough testing across all user input pathways.

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
PhppgadminApplication
Affected:<= 7.13.0

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. Check installed phpPgAdmin version
    Locate the version file (typically version.php in the root directory or check the X-Powered-By header). Common paths: /version.php, /ibraries/Version.class.php, or inspect the page footer for version display.
    Affected if The installed version is 7.13.0 or any earlier version (e.g., 7.12.0, 7.11.0, etc.)
  2. Identify affected PHP files
    Verify the presence of sequences.php, indexes.php, and admin.php in the phpPgAdmin installation directory. These files are typically found in the /browser/ or /src/ subdirectory depending on the installation structure.
    Affected if Any of these files exist in the installation and the version is <= 7.13.0
  3. Examine code for unsanitized $_REQUEST usage
    Open each affected file (sequences.php, indexes.php, admin.php) and search for direct usage of $_REQUEST or $_GET/$_POST parameters embedded in HTML output without htmlspecialchars() or equivalent encoding. Look for patterns like: echo $_REQUEST['param']; or <div><?php echo $_REQUEST['param']; ?></div>
    Affected if The code contains $_REQUEST parameter values reflected directly in HTML output without sanitization functions like htmlspecialchars(), htmlentities(), or equivalent encoding mechanisms
  4. Verify user input pathways are accessible
    Confirm the web application is accessible and these affected files can be reached via HTTP requests. Test accessing the files directly or through the application's navigation to confirm they process and display user-supplied parameters.
    Affected if The affected files are accessible and process user-supplied input from URL parameters without sanitization

You are affected if phpPgAdmin version is 7.13.0 or earlier AND the affected files (sequences.php, indexes.php, admin.php) contain unsanitized $_REQUEST parameters reflected in HTML output.

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 7.13.0
Interim mitigation

Implement proper input validation and output encoding for all user-supplied data before rendering in HTML. Apply context-appropriate escaping functions (such as htmlspecialchars()) to all $_REQUEST parameters in the affected files and conduct thorough testing across all user input pathways.

Recommended fix Moderate confidence

phpPgAdmin > 7.13.0 (latest stable release)

  1. 1. Backup your current phpPgAdmin installation and configuration files
  2. 2. Download the latest stable version of phpPgAdmin from the official repository (github.com/phppgadmin/phppgadmin)
  3. 3. Extract the new version to your web server's document root
  4. 4. Copy your existing configuration file (conf/config.php) to the new installation
  5. 5. Verify file permissions are correct (web server user should have read access)
  6. 6. Test that phpPgAdmin connects to your PostgreSQL server successfully
  7. 7. Verify the application loads without errors in your browser
Caveat Review release notes for any configuration changes required between versions

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

Fix this in Phppgadmin Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60796 — 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-60796 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