dbcve.org
Media ServerApplication · Sick

CVE-2025-49182

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-12
Fix available
A fix is available. Upgrade to 1.5 or later.
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
Files in the source code contain login credentials for the admin user and the property configuration password, allowing an attacker to get full access to the application.

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 confidence

Hardcoded credentials (admin user login and property configuration password) embedded in application source code allow unauthenticated attackers to gain full administrative access to the application.

MitigationRemove all hardcoded credentials from source code files, rotate exposed admin password and configuration password immediately, and implement secure credential management (environment variables, secrets vault, or configuration server).

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 ServerApplication
Affected:< 1.5

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. Identify installed Sick Media Server version
    Locate the Sick Media Server installation and check its version number (typically in application metadata, about page, or version file in the installation directory)
    Affected if Version is below 1.5 (any version < 1.5 is affected)
  2. Locate source code files
    Find the Sick Media Server application source code files on the system - look in installation directory, web root, or application source folder
    Affected if Source code files exist on the system (hardcoded credentials are embedded in the source)
  3. Search for hardcoded credentials in source code
    Search source code files (especially configuration, auth, or user management modules) for strings resembling hardcoded passwords, API keys, or admin credentials - look for patterns like 'password=', 'admin', 'hardcoded', or literal password strings
    Affected if Hardcoded admin login credentials or property configuration passwords are found in source code files
  4. Check admin interface exposure
    Determine if the Sick Media Server admin interface is network-accessible (check firewall rules, network bindings, or service configuration for web port exposure)
    Affected if Admin interface is exposed to network without proper access controls (enables unauthenticated exploitation)
  5. Verify if default admin credentials are active
    Attempt to access admin login or check authentication configuration to determine if default/hardcoded admin credentials remain in use
    Affected if Default admin credentials from hardcoded values are still active and usable

You are affected if Sick Media Server version is below 1.5 AND hardcoded credentials exist in source code AND the admin interface is accessible, allowing unauthenticated attackers to gain full administrative access.

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.

dbcve · scoped
Upgrade available Upgrade to 1.5 or later
Fixed in 1.5
Interim mitigation

Remove all hardcoded credentials from source code files, rotate exposed admin password and configuration password immediately, and implement secure credential management (environment variables, secrets vault, or configuration server).

Recommended fix Moderate confidence

Media Server 1.5 or later

  1. Identify all instances of the Media Server installation in your environment
  2. Check the current installed version of Media Server (typically via about page, CLI, or configuration file)
  3. Review release notes for Media Server version 1.5 for any migration requirements or注意事项
  4. Plan maintenance window as upgrade may require service restart
  5. Download Media Server version 1.5 or later from the official SICK support portal (sick.com or cdn.sick.com)
  6. Stop the Media Server service before upgrading
  7. Perform the upgrade following the official installation/upgrade documentation
  8. After upgrade, immediately change the admin password and any property configuration passwords from their default values
Caveat Review version 1.5 release notes for any breaking changes or deprecated features before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Media Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49182 — 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-49182 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