# CVE-2023-22851: Deserialization in n/a

> An admin can trigger PHP object injection via unserialize in the WordPress importer, potentially leading to code execution.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2023
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-88jc-5fh5-vg3x

## What is CVE-2023-22851?

CVE-2023-22851 is a high-severity unsafe deserialization vulnerability in n/a, published on 14 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Tiki before 24.2 allows lib/importer/tikiimporter_blog_wordpress.php PHP Object Injection by an admin because of an unserialize call.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2023-22851?

It affects 1 product.


Products: Tiki Tiki.

## How do I fix CVE-2023-22851?

No fix has been published for CVE-2023-22851 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-22851 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22851 exists.

## Other vulnerabilities in n/a

- [CVE-2020-15906](https://insights.sbomify.com/CVE-2020-15906/): Auth bypass in n/a (critical 9.8)
- [CVE-2023-22850](https://insights.sbomify.com/CVE-2023-22850/): Deserialization in n/a (high 8.8)
- [CVE-2023-22853](https://insights.sbomify.com/CVE-2023-22853/): Code injection in n/a (high 8.8)
- [CVE-2018-7304](https://insights.sbomify.com/CVE-2018-7304/): Code injection in n/a (high 8.8)
- [CVE-2011-4558](https://insights.sbomify.com/CVE-2011-4558/): Code injection in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22851 and fix it if it is affected.

What it is: CVE-2023-22851 is a high-severity unsafe deserialization vulnerability in n/a, published on 14 Jan 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22851 exists.

Affected product: n/a. 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-2023-22851/ (Markdown: https://insights.sbomify.com/CVE-2023-22851/index.md)
```

## Sources

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

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