# GHSA-c8f7-x2g7-7fxj: Phoenix-ws source code and data in extensions folder is publicly available

> Attackers can access source code and files in the extensions folder via HTTP GET, exposing sensitive application data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Jun 2022

## What is GHSA-c8f7-x2g7-7fxj?

GHSA-c8f7-x2g7-7fxj is a vulnerability in phoenix-ws, published on 2 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Impact
All of the source code, files, and folders in `phoenix_files/extensions/` are available to end users through a simple HTTP GET request.

### Patches
The issue has been patched. The users of version 1.0.6 and above are not effected.

## Which versions are affected by GHSA-c8f7-x2g7-7fxj?

2 open source packages ship an affected version, including phoenix-ws.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `phoenix-ws` | PyPI | All versions | 1.0.6 |
| `phoenix-ws` | PyPI | All versions | 1.0.6 |

## How do I fix GHSA-c8f7-x2g7-7fxj?

Upgrade phoenix-ws to 1.0.6 or later.

## Is GHSA-c8f7-x2g7-7fxj being exploited?

There is no known exploitation of GHSA-c8f7-x2g7-7fxj in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-c8f7-x2g7-7fxj and fix it if it is affected.

What it is: GHSA-c8f7-x2g7-7fxj is a vulnerability in phoenix-ws, published on 2 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-c8f7-x2g7-7fxj in the wild and no public exploit code.

Affected packages and fixed versions:
- phoenix-ws (PyPI): affected all versions; fixed in 1.0.6
- phoenix-ws (PyPI): affected all versions; fixed in 1.0.6

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/GHSA-c8f7-x2g7-7fxj/ (Markdown: https://insights.sbomify.com/GHSA-c8f7-x2g7-7fxj/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-c8f7-x2g7-7fxj

---
From sbomify Insights: https://insights.sbomify.com/GHSA-c8f7-x2g7-7fxj/
Summaries are generated and may contain mistakes; the official description above is the record.