# CVE-2025-1113: taisan tarzan-cms Add Theme admin#themes upload deserialization

> Remote attackers can achieve code execution via unsafe deserialization in the tarzan-cms Add Theme upload handler.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Feb 2025
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-9crj-f7wm-748r

## What is CVE-2025-1113?

CVE-2025-1113 is a medium-severity unsafe deserialization vulnerability in taisan tarzan-cms, published on 7 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in taisan tarzan-cms up to 1.0.0. It has been rated as critical. This issue affects the function upload of the file /admin#themes of the component Add Theme Handler. The manipulation leads to deserialization. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-1113?

It affects 1 product.


Products: Taisan Tarzan-Cms.

## How do I fix CVE-2025-1113?

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

## Is CVE-2025-1113 being exploited?

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

## Other vulnerabilities in taisan tarzan-cms

- [CVE-2024-13022](https://insights.sbomify.com/CVE-2024-13022/): taisan tarzan-cms Article Management UploadController.java UploadResponse unrestricted upload (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1113 and fix it if it is affected.

What it is: CVE-2025-1113 is a medium-severity unsafe deserialization vulnerability in taisan tarzan-cms, published on 7 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1113 exists.

Affected product: taisan tarzan-cms. 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-2025-1113/ (Markdown: https://insights.sbomify.com/CVE-2025-1113/index.md)
```

## Sources

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

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