CVE-2025-5380
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, which was classified as critical, has been found in ashinigit 天青一白 XueShengZhuSu 学生住宿管理系统 up to 4d3f0ada0e71482c1e51fd5f5615e5a3d8bcbfbb. This issue affects some unknown processing of the file /upload/ of the component Image File Upload. The manipulation of the argument File leads to path traversal. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not 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 · moderate confidenceA path traversal vulnerability exists in the image file upload component at the /upload/ endpoint of the student accommodation management system. Attackers can manipulate the 'File' argument using directory traversal sequences (e.g., ../../) to write files outside the intended upload directory, potentially overwriting system files or accessing sensitive data.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify the /upload/ endpoint existsReview web server access logs or application routing configuration for requests to /upload/ or /upload endpoint pathsAffected if The endpoint is accessible and actively handles file uploads in the student accommodation management system
-
Identify the application versionCheck the installed version of the student accommodation management system through the admin interface, about page, or application banner. Compare against any known affected version range if documented.Affected if The installed version is within the affected range for this vulnerability
-
Inspect the upload component codeLocate and review the file upload handler at the /upload/ endpoint. Look for how the 'File' parameter is processed and whether directory traversal sequences are validated or sanitized.Affected if The code does not validate or reject directory traversal sequences like ../ in the filename parameter
-
Check upload directory configurationExamine the application's configuration to determine where uploaded files are stored and whether the upload directory is within the web root or has restricted write permissions.Affected if The upload directory permits write access outside its intended boundaries or is not restricted to safe paths
-
Test for path traversal vulnerabilitySend a test file upload request to /upload/ with a manipulated filename containing ../../ sequences. Verify if files can be written outside the intended upload directory.Affected if Files can be written to directories outside the designated upload folder using traversal sequences
A user is affected if the student accommodation management system exposes an accessible /upload/ endpoint that does not properly validate or reject directory traversal sequences in the File parameter, allowing files to be written outside the intended upload directory.
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 input validation on the file upload functionality to sanitize file paths, whitelist allowed directories, and reject paths containing traversal sequences. Additionally, enforce file type validation and store uploads outside the web root.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5380 — 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-5380 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