CVE-2026-13547
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 determined in Hanwang e-Face General Management Platform 6.3.5.4. This issue affects some unknown processing of the file /manage/resourceUpload/upload.do. Executing a manipulation of the argument File can lead to unrestricted upload. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized.
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 confidenceUnrestricted file upload vulnerability in Hanwang e-Face General Management Platform 6.3.5.4 allows remote attackers to upload arbitrary files via manipulation of the File parameter in the /manage/resourceUpload/upload.do endpoint, potentially enabling remote code execution.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify installed Hanwang e-Face platform versionCheck the application's about page, banner, or version file. Common locations include the login page source, /manage/about.do, or check the WAR file version if accessible via server file system.Affected if The installed version is 6.3.5.4 or falls within an unspecified version range around 6.3.5.4.
-
Verify /manage/resourceUpload/upload.do endpoint existsSend an HTTP GET or POST request to https://target/manage/resourceUpload/upload.do and observe the response. A 200 OK or any response other than 404 indicates the endpoint is present.Affected if The endpoint returns any response other than 404 Not Found, meaning the upload functionality exists.
-
Confirm file upload functionality is enabledAttempt a test file upload to the /manage/resourceUpload/upload.do endpoint using a benign file (e.g., a small text file). Check if the upload is accepted or if the endpoint rejects the request.Affected if The endpoint accepts file uploads without requiring authentication or returns an upload success response.
-
Check upload storage location configurationInspect the application configuration files (e.g., web.xml, application.properties, or platform-specific config) to determine where uploaded files are stored. Access the upload directory directly via HTTP if possible.Affected if Uploaded files are stored within the webroot or a publicly accessible directory, allowing the uploaded file to be accessed via HTTP for RCE.
A system is affected if it runs Hanwang e-Face General Management Platform 6.3.5.4 (or an adjacent vulnerable version) and the /manage/resourceUpload/upload.do endpoint is accessible and functional for unauthenticated file 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 dataRestrict or disable the file upload functionality at /manage/resourceUpload/upload.do; implement strict allowlist-based file type validation, store uploads outside webroot, and apply vendor security patches when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13547 — 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-2026-13547 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