CVE-2025-7627
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 · uneditedA vulnerability was found in YiJiuSmile kkFileViewOfficeEdit up to 5fbc57c48e8fe6c1b91e0e7995e2d59615f37abd and classified as critical. Affected by this issue is the function fileUpload of the file /fileUpload. The manipulation of the argument File leads to unrestricted upload. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available.
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 confidenceUnrestricted file upload vulnerability in the fileUpload function at /fileUpload endpoint of YiJiuSmile kkFileViewOfficeEdit. Attackers can manipulate the File argument to upload arbitrary files to the server, potentially leading to remote code execution if executable files are uploaded and accessed.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2019-03-19CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify /fileUpload endpoint is exposedAttempt to access the /fileUpload endpoint via HTTP request (e.g., curl http://target/fileUpload or check web server access logs for requests to this endpoint)Affected if The endpoint is reachable without authentication and accepts POST requests with a File parameter
-
Identify installed kkFileViewOfficeEdit versionCheck the application version by reviewing deployment metadata, JAR file names, build artifacts, or the application's About/Info page if availableAffected if The installed version is dated 2019-03-19 or earlier (any version <= 2019-03-19)
-
Confirm file upload functionality accepts arbitrary extensionsSend a test POST request to /fileUpload with a File parameter containing a file with an executable extension (e.g., .jsp, .php, .exe) and observe if the server accepts and stores itAffected if The server accepts and stores files with potentially executable extensions without validation
-
Check uploaded files are web-accessible with script executionAfter uploading a test file, determine its storage location by accessing it via URL; verify if the upload directory is within the webroot and if server-side script execution is enabled for that directoryAffected if Uploaded files are stored within the webroot and the server executes scripts from that directory
-
Verify authentication is required for file uploadAttempt to access /fileUpload without providing valid credentials, session cookies, or API keys; check if the request is rejected or requires authenticationAffected if The /fileUpload endpoint accepts requests without any authentication or authorization checks
A user is affected if they are running kkFileViewOfficeedit version 2019-03-19 or earlier with the /fileUpload endpoint exposed and no authentication enforced on uploads.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict file type validation (extension, MIME type, magic bytes), add authentication/authorization checks to the upload endpoint, store uploaded files outside webroot with disabled script execution, and consider implementing a Web Application Firewall as an additional layer of protection.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7627 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7627 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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