# CVE-2023-7305: SmartBI RMIServlet Unrestricted File Upload RCE

> Attackers can upload malicious files to SmartBI to execute arbitrary code on the host, requiring specific configurations.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/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 Oct 2025
- **Updated:** 7 Nov 2025
- **Also known as:** GHSA-75gf-3x5v-8fcm

## What is CVE-2023-7305?

CVE-2023-7305 is a critical vulnerability in Guangzhou Smart Software Co., Ltd. SmartBI, published on 15 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SmartBI V8, V9, and V10 contain an unrestricted file upload vulnerability via the RMIServlet request handling logic. Under certain configurations or usage patterns, attackers can send specially crafted requests that cause the application to perform sensitive operations or execute arbitrary code on the host. The vendor released a fix in July 2023 to address the underlying flaw. VulnCheck has observed this vulnerability being exploited in the wild.

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

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


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

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

## Is CVE-2023-7305 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-7305 is a critical vulnerability in Guangzhou Smart Software Co., Ltd. SmartBI, published on 15 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-7305 exists.

Affected product: Guangzhou Smart Software Co., Ltd. SmartBI. 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-7305/ (Markdown: https://insights.sbomify.com/CVE-2023-7305/index.md)
```

## Sources

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

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