CVE-2025-15152
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 identified in h-moses moga-mall up to 392d631a5ef15962a9bddeeb9f1269b9085473fa. This vulnerability affects the function addProduct of the file src/main/java/com/ms/product/controller/PmsProductController.java. Such manipulation of the argument objectName leads to unrestricted upload. The attack may be performed from remote. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed.
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 addProduct function of PmsProductController.java. The objectName parameter is not validated, allowing remote attackers to upload arbitrary files to the server by manipulating this argument.
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.
-
Locate the PmsProductController.java fileSearch the application source code for the file PmsProductController.java, typically found under src/main/java in a web controller packageAffected if The file exists and contains an addProduct method handling file uploads
-
Identify the addProduct endpointExamine the addProduct method for @PostMapping or @RequestMapping annotations indicating it accepts HTTP POST requestsAffected if The endpoint is exposed and accessible via HTTP POST to /product/add or similar path
-
Verify objectName parameter usageInspect the addProduct method signature for an objectName parameter (or similar filename parameter) and trace how it is used in file handling codeAffected if The objectName parameter is passed directly to file operations without validation
-
Check for file type/extension validationSearch the addProduct method for allowlist validation logic (e.g., checking file extensions, MIME types) on the objectName or uploaded fileAffected if No allowlist validation exists for file types/extensions on the objectName parameter
-
Confirm file upload functionality is enabledVerify the application has file upload libraries configured (e.g., Spring CommonsMultipartResolver, MultipartConfigElement) and the addProduct method accepts MultipartFileAffected if File upload is enabled and the addProduct method processes MultipartFile uploads without sanitizing objectName
Your environment is affected if the PmsProductController.java addProduct method accepts file uploads via an objectName parameter without validating the filename against an allowlist of permitted extensions.
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 validation for the objectName parameter: validate file types/extensions against an allowlist, sanitize filenames to prevent path traversal, store uploads outside the web root, and enforce size limits.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15152 — 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-15152 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