# CVE-2023-53871: Soosyze 2.0.0 Unrestricted File Upload via Broken Upload Logic

> Attackers can upload malicious PHP files to execute code and view sensitive paths in Soosyze CMS.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-xjx3-pxg9-f9p4

## What is CVE-2023-53871?

CVE-2023-53871 is a medium-severity vulnerability in Soosyze, published on 15 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Soosyze 2.0.0 contains a file upload vulnerability that allows attackers to upload arbitrary HTML files with embedded PHP code to the application. Attackers can exploit the broken file upload mechanism to potentially view sensitive file paths and execute malicious PHP scripts on the server.

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

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

It affects 1 product.


Products: Soosyze Soosyze.

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

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

## Is CVE-2023-53871 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-53871 is a medium-severity vulnerability in Soosyze, published on 15 Dec 2025. 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-2023-53871 in the wild and no public exploit code.

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

## Sources

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

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