Skip to content
Fencer Vulns
medium 6.5

CVE-2023-0241 json

pgAdmin 4 vulnerable to directory traversal

published 2023-03-27 3 y ago modified 2026-07-07 4 mo ago also GHSA-9crj-hpxh-f6qg , PYSEC-2026-1771 , EUVD-2023-0964

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
8.8%
EPSS 8.8% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi pgadmin4 6.19
  • pgadmin pgadmin_4 6.19
  • pgadmin4 SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE Real Time 15 SP3 +7 more 4.30-150300.3.9.1

suse advisories SUSE-SU-2023:1877-1

  • pgadmin4 openSUSE Tumbleweed 8.2-1.1

opensuse advisories openSUSE-SU-2024:13667-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-0241 updated cvss 3.1

pgadmin4: directory traversal vulnerability

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
20 mo ago

Exploit prediction

8.83% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
pypi pgadmin4
<6.19
6.19

Affected products

  • n/a pgadmin

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.