dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2023-7330

CRITICAL · 9.3 CVSS v4.0 Published 2025-11-24
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
Ruijie NBR series routers contain an unauthenticated arbitrary file upload vulnerability via /ddi/server/fileupload.php. The endpoint accepts attacker-supplied values in the name and uploadDir parameters and saves the provided multipart file content without adequate validation or sanitization of file type, path, or extension. A remote attacker can upload a crafted PHP file and then access it from the web root, resulting in arbitrary code execution in the context of the web service. Exploitation evidence was observed by the Shadowserver Foundation on 2025-01-14 UTC.

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 · high confidence

Ruijie NBR series routers contain an unauthenticated arbitrary file upload vulnerability in the /ddi/server/fileupload.php endpoint. The affected component accepts attacker-controlled values in the 'name' and 'uploadDir' parameters and stores uploaded multipart file content without validating file type, path, or extension. A remote unauthenticated attacker can upload a crafted PHP file to the web root and execute it, achieving arbitrary code execution in the context of the web service. Shadowserver Foundation observed active exploitation of this vulnerability on 2025-01-14.

MitigationApply vendor-supplied patches for Ruijie NBR routers; if no patch is available, disable or block external access to the /ddi/server/fileupload.php endpoint via firewall or WAF rules and consider network segmentation to limit exposure of management interfaces.

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:N/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 Ruijie NBR router exposure
    Determine if the Ruijie NBR device management interface is accessible from untrusted networks by scanning for HTTP/HTTPS services on the public IP or testing access to the device's web interface from external networks.
    Affected if The device management interface is directly accessible from the internet or untrusted networks.
  2. Verify fileupload endpoint exists
    Attempt to access the path /ddi/server/fileupload.php on the Ruijie NBR web server (e.g., curl -I http://<device-ip>/ddi/server/fileupload.php). Check if the endpoint responds (200, 404, or other status).
    Affected if The endpoint returns any response other than a clear 'not found' 404, indicating the vulnerable script exists on the system.
  3. Check for unauthorized PHP files in web root
    If you have administrative access, examine the web root directory (typically /www or /htdocs) for unexpected .php files with names that do not match legitimate router firmware files. Look for files created recently or with random/encoded names.
    Affected if Unexpected PHP files exist in the web root that were not installed as part of the official firmware.
  4. Review access logs for fileupload activity
    Examine web server access logs (typically stored in /var/log or /ddi/logs) for requests to /ddi/server/fileupload.php, especially with unusual 'name' or 'uploadDir' parameters or requests originating from external IP addresses.
    Affected if There are logged requests to the fileupload endpoint from untrusted or unknown IP addresses, particularly with multipart file uploads.
  5. Compare installed firmware version
    Access the router administration panel and check the firmware version under System Status or Management settings. Compare this version against any vendor advisories for CVE-2023-7330 or contact Ruijie support to confirm if the version is affected.
    Affected if The installed firmware version has not been patched to address the arbitrary file upload vulnerability.

A Ruijie NBR router is affected if it is directly exposed to untrusted networks, the /ddi/server/fileupload.php endpoint exists, and the firmware version predates available patches for this vulnerability.

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

Apply vendor-supplied patches for Ruijie NBR routers; if no patch is available, disable or block external access to the /ddi/server/fileupload.php endpoint via firewall or WAF rules and consider network segmentation to limit exposure of management interfaces.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-7330 — 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-7330 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