# GHSA-q3jm-v27q-jfww: titon/framework vulnerable to Remote Code Execution via Chosen-Ciphertext Attack

> Abandoned PHP framework allows remote code execution via chosen-ciphertext attack, requiring migration to maintained alternatives.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2024

## What is GHSA-q3jm-v27q-jfww?

GHSA-q3jm-v27q-jfww is an unsafe deserialization vulnerability in titon/framework, published on 30 May 2024. It can be exploited over the network, with no action from the victim.

### Official description

titon/framework package (which is now abandoned and no longer maintained) is vulnerable to remote code execution via Chosen-Ciphertext Attack.

## Which versions are affected by GHSA-q3jm-v27q-jfww?

2 open source packages ship an affected version, including titon/framework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `titon/framework` | Packagist | All versions to 0.1.0-alpha | None |
| `titon/framework` | Packagist | All versions to 0.1.0-alpha | None |

## How do I fix GHSA-q3jm-v27q-jfww?

No fix has been published for GHSA-q3jm-v27q-jfww yet. Limit exposure of the affected software until one is available.

## Is GHSA-q3jm-v27q-jfww being exploited?

There is no known exploitation of GHSA-q3jm-v27q-jfww in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-q3jm-v27q-jfww and fix it if it is affected.

What it is: GHSA-q3jm-v27q-jfww is an unsafe deserialization vulnerability in titon/framework, published on 30 May 2024. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-q3jm-v27q-jfww in the wild and no public exploit code.

Affected packages and fixed versions:
- titon/framework (Packagist): affected all versions up to 0.1.0-alpha; no fix listed
- titon/framework (Packagist): affected all versions up to 0.1.0-alpha; no fix listed

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-q3jm-v27q-jfww/ (Markdown: https://insights.sbomify.com/GHSA-q3jm-v27q-jfww/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-q3jm-v27q-jfww

---
From sbomify Insights: https://insights.sbomify.com/GHSA-q3jm-v27q-jfww/
Summaries are generated and may contain mistakes; the official description above is the record.