# CVE-2019-15521: Spoon Library as used in Fork CMS allows PHP object injection

> Attackers can achieve code execution by sending a malicious serialized object in a cookie to applications using the vulnerable Spoon Library.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2p2x-mw56-jc98

## What is CVE-2019-15521?

CVE-2019-15521 is a critical unsafe deserialization vulnerability in n/a, published on 26 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Spoon Library through 2014-02-06, as used in Fork CMS before 1.4.1 and other products, allows PHP object injection via a cookie containing an object.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2019-15521?

2 open source packages ship an affected version, including spoon/library. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `spoon/library` | Packagist | All versions | 1.4.1 |
| `spoon/library` | Packagist | All versions | 1.4.1 |

Products: Fork-Cms Fork Cms, Spoon-Library Spoon Library.

## How do I fix CVE-2019-15521?

Upgrade spoon/library to 1.4.1 or later.

## Is CVE-2019-15521 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-0153](https://insights.sbomify.com/CVE-2022-0153/): SQL Injection in forkcms/forkcms (critical 9.6)
- [CVE-2022-1064](https://insights.sbomify.com/CVE-2022-1064/): SQL injection through marking blog comments on bulk as spam in forkcms/forkcms (critical 9.0)
- [CVE-2021-28931](https://insights.sbomify.com/CVE-2021-28931/): Arbitrary file upload in Fork CMS (high 8.8)
- [CVE-2020-23264](https://insights.sbomify.com/CVE-2020-23264/): Cross-Site Request Forgery in forkcms (high 8.8)
- [CVE-2020-24036](https://insights.sbomify.com/CVE-2020-24036/): Deserialization in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15521 and fix it if it is affected.

What it is: CVE-2019-15521 is a critical unsafe deserialization vulnerability in n/a, published on 26 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-15521 in the wild and no public exploit code.

Affected packages and fixed versions:
- spoon/library (Packagist): affected all versions; fixed in 1.4.1
- spoon/library (Packagist): affected all versions; fixed in 1.4.1

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-2019-15521/ (Markdown: https://insights.sbomify.com/CVE-2019-15521/index.md)
```

## Sources

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

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