dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-34046

CRITICAL · 10.0 CVSS v4.0 Published 2025-06-26
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
An unauthenticated file upload vulnerability exists in the Fanwei E-Office <= v9.4 web management interface. The vulnerability affects the /general/index/UploadFile.php endpoint, which improperly validates uploaded files when invoked with certain parameters (uploadType=eoffice_logo or uploadType=theme). An attacker can exploit this flaw by sending a crafted HTTP POST request to upload arbitrary files without requiring authentication. Successful exploitation could enable remote code execution on the affected server, leading to complete compromise of the web application and potentially the underlying system. Exploitation evidence was observed by the Shadowserver Foundation on 2025-02-05 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

Unauthenticated file upload vulnerability in Fanwei E-Office v9.4 and below allows attackers to upload arbitrary files via the /general/index/UploadFile.php endpoint by manipulating the uploadType parameter (eoffice_logo or theme). The lack of authentication and file validation enables direct upload of malicious files, potentially leading to remote code execution and complete system compromise.

MitigationImmediately restrict network access to the /general/index/UploadFile.php endpoint, disable file upload functionality if possible, and apply vendor-provided patch or upgrade to a fixed version of Fanwei E-Office.

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:H/SI:H/SA:H/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 the installed Fanwei E-Office version
    Check the version banner or version file in the web application root directory. Common locations include a version info file, about page, or check the HTTP server headers. Look for version display in the application interface under Help or About sections.
    Affected if The installed version is Fanwei E-Office v9.4 or below, or if the version cannot be determined but the product is confirmed as Fanwei E-Office.
  2. Verify the vulnerable UploadFile.php endpoint exists
    Attempt to access the URL path /general/index/UploadFile.php on the web server. Check if the endpoint responds (even with an error) rather than returning a 404 Not Found.
    Affected if The endpoint returns any response (including error messages) indicating the file exists, which means the vulnerable script is present.
  3. Test if the uploadType parameter is accepted
    Send a POST request to /general/index/UploadFile.php with a simple test file and the uploadType parameter set to either 'eoffice_logo' or 'theme'. Observe if the application processes the request without rejecting the parameter.
    Affected if The application accepts the uploadType parameter and processes the upload request, indicating the vulnerable parameter handling is active.
  4. Inspect upload directories for unexpected files
    Examine the directories where uploaded files are stored. Common paths may include /uploads/, /attachment/, or similar directories configured for the application. Look for file types that should not be present such as .php, .asp, .exe, or other executable extensions.
    Affected if Any suspicious script files (especially web shell files) are found in upload directories, indicating the vulnerability may have been exploited.

A user is affected if Fanwei E-Office v9.4 or below is installed and the /general/index/UploadFile.php endpoint is accessible, as the unauthenticated file upload vulnerability can be exploited.

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 restrict network access to the /general/index/UploadFile.php endpoint, disable file upload functionality if possible, and apply vendor-provided patch or upgrade to a fixed version of Fanwei E-Office.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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