dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2023-7305

CRITICAL · 9.2 CVSS v4.0 Published 2025-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SmartBI V8-V10 contains an unrestricted file upload vulnerability in the RMIServlet request handling logic. Attackers can send specially crafted requests to upload malicious files and achieve arbitrary code execution on the host. This critical (CVSS 9.2) vulnerability has been observed being exploited in the wild.

MitigationImmediately apply the vendor patch released in July 2023 and verify the RMIServlet configuration restricts file uploads. If patching is not possible, disable or restrict access to the RMIServlet endpoint until a patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SmartBI installation version
    Locate the SmartBI installation directory and check version files (typically version.properties, version.txt, or the application's main JAR file name). Alternatively, access the application's login page or admin panel which often displays the version number.
    Affected if The installed version falls within V8 through V10 (any version between 8.0 and 10.x inclusive)
  2. Locate and inspect RMIServlet configuration
    Search for servlet configuration files in the SmartBI deployment (typically in WEB-INF/web.xml or similar servlet mapping files). Identify if RMIServlet is mapped and note its URL pattern (commonly /RMIServlet or similar).
    Affected if RMIServlet is mapped and accessible in the web.xml configuration
  3. Verify RMIServlet file upload functionality is exposed
    Check network accessibility of the RMIServlet endpoint by reviewing server access controls, firewall rules, or reverse proxy configurations. Attempt a controlled HTTP request to the RMIServlet URL if authorized.
    Affected if The RMIServlet endpoint is reachable from the network without authentication or additional access controls
  4. Inspect upload directories for suspicious files
    Examine common file upload directories within the SmartBI installation (such as temp folders, upload directories, or the web root). Look for unexpected file types (jsp, exe, shell scripts) or recently created executable files.
    Affected if Unexpected or malicious files exist in upload directories, particularly web-accessible paths
  5. Review server logs for RMIServlet upload attempts
    Search application and web server logs (typically in logs/ or tomcat/logs/) for requests to RMIServlet containing upload-related parameters or file upload patterns.
    Affected if Log entries show unauthorized file upload requests to RMIServlet from unexpected sources

You are affected if SmartBI V8-V10 is installed AND the RMIServlet is exposed with unrestricted file upload capability, or if malicious files are found in the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately apply the vendor patch released in July 2023 and verify the RMIServlet configuration restricts file uploads. If patching is not possible, disable or restrict access to the RMIServlet endpoint until a patch can be applied.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-7305 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-7305 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data