# CVE-2024-6238: pgAdmin 4 Installation Directory permission issue

> Attackers can gain unauthorized access to the pgAdmin 4 installation directory on Debian or RHEL 8 due to improper permissions.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2024
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-783m-7jjf-pmgr

## What is CVE-2024-6238?

CVE-2024-6238 is a high-severity vulnerability in pgadmin.org pgAdmin 4, published on 25 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

pgAdmin <= 8.8 has an installation Directory permission issue. Because of this issue, attackers can gain unauthorised access to the installation directory on the Debian or RHEL 8 platforms.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2024-6238?

It affects 1 product.


Products: Pgadmin Pgadmin 4.

## How do I fix CVE-2024-6238?

Apply the vendor's patch.

## Is CVE-2024-6238 being exploited?

There is no known exploitation of CVE-2024-6238 in the wild and no public exploit code.

## Other vulnerabilities in pgadmin.org pgAdmin 4

- [CVE-2025-2945](https://insights.sbomify.com/CVE-2025-2945/): pgAdmin 4: Remote Code Execution in Query Tool and Cloud Deployment (critical 9.9)
- [CVE-2024-9014](https://insights.sbomify.com/CVE-2024-9014/): OAuth2 client id and secret exposed through the web browser in pgAdmin 4 (critical 9.9)
- [CVE-2026-12046](https://insights.sbomify.com/CVE-2026-12046/): Deserialization in pgAdmin 4 (critical 9.5)
- [CVE-2026-17351](https://insights.sbomify.com/CVE-2026-17351/): SQL injection in pgAdmin 4 (critical 9.4)
- [CVE-2026-17566](https://insights.sbomify.com/CVE-2026-17566/): Command injection in pgAdmin 4 (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6238 and fix it if it is affected.

What it is: CVE-2024-6238 is a high-severity vulnerability in pgadmin.org pgAdmin 4, published on 25 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6238 in the wild and no public exploit code.

Affected product: pgadmin.org pgAdmin 4. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-6238/ (Markdown: https://insights.sbomify.com/CVE-2024-6238/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6238
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6238
- OSV: https://osv.dev/vulnerability/CVE-2024-6238

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-6238/
Summaries are generated and may contain mistakes; the official description above is the record.