CVE-2025-14965
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 1541492390c yougou-mall up to 0a771fa817c924efe52c8fe0a9a6658eee675f9f. This impacts the function upload/delete of the file src/main/java/per/ccm/ygmall/extra/controller/ResourceController.java. Performing manipulation results in path traversal. 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 · moderate confidencePath traversal vulnerability in the file upload/delete function of ResourceController.java in yougou-mall. An attacker can manipulate file path parameters to access or overwrite files outside the intended directory, potentially leading to unauthorized file system access.
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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:A/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.
-
Locate ResourceController.java in the yougou-mall deploymentSearch the application source code or WAR/jar archive for the file ResourceController.java. If the application is deployed, check the application directory structure for controllers handling file operations.Affected if The file ResourceController.java exists and contains file upload/delete handlers without path validation logic.
-
Identify file upload/delete endpoint configurationExamine ResourceController.java for methods handling file upload or deletion. Look for @RequestMapping, @PostMapping, @GetMapping, or @DeleteMapping annotations that expose file operation endpoints.Affected if File upload/delete endpoints are exposed (e.g., /resource/upload, /resource/delete) that accept a file path parameter.
-
Check for path traversal protection in the codeReview the file operation logic in ResourceController.java for path validation. Search for canonicalization (getCanonicalPath), path validation, or directory restriction checks before performing file operations.Affected if No path validation, canonicalization, or directory restriction is implemented before file operations, or validation can be bypassed.
-
Verify allowed directory configurationLook for configuration defining allowed upload directories (e.g., uploadDir, basePath, allowedPath). Check if uploaded/deleted files are restricted to a specific base directory.Affected if No explicit allowed directory is defined, or the file path parameter can escape the intended directory using ../ sequences.
-
Test path traversal vulnerability (if authorized)If you have authorization, send a request to the file upload/delete endpoint with a path parameter containing ../ sequences (e.g., ../../etc/passwd) to see if files outside the intended directory can be accessed or overwritten.Affected if The application allows path traversal sequences in the file path parameter, allowing access to files outside the intended upload directory.
If yougou-mall is deployed with ResourceController.java exposing file upload/delete endpoints that accept path parameters without strict path validation or directory restriction, the environment is affected by CVE-2025-14965.
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 path validation and canonicalization on file paths before upload/delete operations. Restrict file operations to explicitly allowed directories and validate path traversal sequences (../) to prevent directory escape.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14965 — 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-14965 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