dbcve.org
Media Convergence SystemApplication · Sobey

CVE-2025-14182

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability has been found in Sobey Media Convergence System 2.0/2.1. This vulnerability affects unknown code of the file /sobey-mchEditor/watermark/upload. The manipulation of the argument File leads to path traversal. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

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 confidence

A path traversal vulnerability exists in Sobey Media Convergence System 2.0/2.1 within the watermark upload functionality at /sobey-mchEditor/watermark/upload. Attackers can manipulate the File argument to traverse directories and write files to arbitrary locations on the server.

MitigationRestrict network access to affected systems, implement strict input validation and path sanitization on file upload parameters to prevent directory traversal sequences, and apply vendor patches when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Media Convergence SystemApplication
Affected:= 2.0= 2.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Sobey Media Convergence System installation
    Check for the presence of Sobey Media Convergence System in your environment by looking for installation directories (commonly under C:\Program Files\Sobey or similar), the 'sobey-mchEditor' web application folder, or the MCH service running on the server.
    Affected if The application is installed and the web component 'sobey-mchEditor' exists in the webroot.
  2. Identify installed version
    Locate and read the version information - typically found in an About dialog within the application, a version.txt file in the installation directory, or the assembly version in the bin folder. Compare against the affected versions (2.0 or 2.1).
    Affected if The installed version is exactly 2.0 or exactly 2.1.
  3. Verify watermark upload endpoint exists
    Check if the /sobey-mchEditor/watermark/upload path is present in the web application's routing configuration or accessible via the web server. This is typically found in the web.config or route definitions of the sobey-mchEditor application.
    Affected if The watermark upload endpoint /sobey-mchEditor/watermark/upload is present and routable in the application.
  4. Check watermark upload functionality accessibility
    Examine the application's authentication and authorization configuration for the watermark upload functionality to determine if it requires authentication or is exposed without proper access controls.
    Affected if The watermark upload endpoint is accessible without authentication or to untrusted users.
  5. Inspect upload handling configuration
    Review the file upload handler code or configuration for the watermark feature to see if input validation on the File parameter includes path traversal sanitization (checking for ../ sequences or absolute path manipulation).
    Affected if The upload handler does not sanitize the File parameter to prevent directory traversal sequences.

You are affected if Sobey Media Convergence System version 2.0 or 2.1 is installed and the /sobey-mchEditor/watermark/upload endpoint is accessible without proper path traversal sanitization on the File parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to affected systems, implement strict input validation and path sanitization on file upload parameters to prevent directory traversal sequences, and apply vendor patches when available.

Fix this in Media Convergence System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14182 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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