CVE-2025-14182
BaseFortify
Publication date: 2025-12-07
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sobey | media_convergence_system | 2.0 |
| sobey | media_convergence_system | 2.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Sobey Media Convergence System 2.0/2.1, specifically in the file /sobey-mchEditor/watermark/upload. It involves manipulation of the 'File' argument leading to a path traversal vulnerability, which allows an attacker to access files and directories outside the intended scope. The attack can be performed remotely and the exploit has been publicly disclosed.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to traverse directories and potentially access sensitive files on the server remotely. This can lead to unauthorized information disclosure, modification, or other malicious actions depending on the files accessed.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability can be detected by monitoring for requests to the endpoint `/sobey-mchEditor/watermark/upload` that contain path traversal sequences in the filename, such as "../../" or multiple "../" segments. A suggested detection method includes using asset mapping queries like `fofa body="/Sc-TaskMonitoring/" || header="Sobey"` to identify affected hosts. Additionally, inspecting web server logs for POST requests with suspicious multipart/form-data uploads containing filenames with path traversal payloads can help detect exploitation attempts. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or disabling the vulnerable file upload functionality at `/sobey-mchEditor/watermark/upload` if possible, applying strict validation and filtering on uploaded filenames to prevent path traversal sequences, and monitoring for suspicious upload activity. Since no official patches or mitigations are documented, consider isolating or replacing the affected Sobey Media Convergence System versions 2.0 and 2.1. Additionally, monitor for any uploaded malicious scripts and remove them promptly to prevent remote code execution. [3, 2]