What is the CVSS score of CVE-2025-49182?

CVE-2025-49182 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.2%.

Which versions of Media Server are affected by CVE-2025-49182?

CVE-2025-49182 exposes hardcoded administrative credentials in application source code, allowing unauthenticated attackers to gain full administrative access without authentication.. A patch is available.

How to fix or mitigate CVE-2025-49182?

Within 24 hours: Identify all systems running affected versions and isolate or restrict network access to administrative interfaces. Within 7 days: Apply vendor-released patch to all affected instances and rotate all administrative credentials post-remediation. Within 30 days: Conduct source code audit across all applications to identify and eliminate additional hardcoded credentials; implement secrets management solution (e.g., HashiCorp Vault, AWS Secrets Manager) and enforce code review controls to prevent recurrence.

Media Server CVE-2025-49182

EUVD-2025-18174 HIGH

Inclusion of Sensitive Information in Source Code (CWE-540)

2025-06-12 psirt@sick.de

Information Disclosure Authentication Bypass Media Server

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 06:39 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

1.5

EUVD ID Assigned

Mar 14, 2026 - 21:20 euvd

EUVD-2025-18174

Analysis Generated

Mar 14, 2026 - 21:20 vuln.today

CVE Published

Jun 12, 2025 - 14:15 nvd

HIGH 7.5

DescriptionCVE.org

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.

AnalysisAI

Critical credential exposure vulnerability where admin login credentials and property configuration passwords are embedded directly in source code, enabling unauthenticated remote attackers to gain full administrative access to the affected application. The vulnerability has a CVSS score of 7.5 (High) with a network attack vector requiring no privileges or user interaction. While specific KEV/EPSS data and POC availability are not provided in the input, the presence of hardcoded credentials in source code represents a severe and often easily discoverable weakness that typically sees rapid exploitation once disclosed.

Technical ContextAI

This vulnerability stems from CWE-540 (Inclusion of Sensitive Information in Source Code), a well-known secure coding anti-pattern where authentication credentials and sensitive configuration data are hardcoded into application source files rather than externalized through environment variables, configuration management systems, or secure vaults. The root cause involves developers committing plaintext credentials to version control systems (Git, SVN, etc.) or embedding them in compiled binaries/JAR files. Without specific CPE data provided, the affected product likely encompasses web applications, APIs, or backend services that rely on admin authentication. The vulnerability is particularly dangerous because source code is often accessible through multiple attack vectors: exposed Git repositories, decompiled binaries, container image inspection, or insider access.

RemediationAI

Immediate remediation steps (in priority order): (1) ROTATE ALL CREDENTIALS IMMEDIATELY—reset admin passwords, regenerate API keys, and revoke any tokens that were exposed in source code; (2) Search all Git history and branches using tools like 'git log -p' or TruffleHog to identify when credentials were introduced and revoke them from all environments; (3) Implement pre-commit hooks (e.g., detect-secrets, git-secrets) to prevent future credential commits; (4) Remove credentials from source code and implement secure credential management: use environment variables, HashiCorp Vault, AWS Secrets Manager, or similar; (5) Audit all access logs and authentication records from the exposure window to detect compromise; (6) If source code was public, assume credential compromise and rotate all downstream systems (databases, APIs, cloud accounts); (7) Apply vendor patches once released (specific patch versions unavailable without vendor advisory); (8) Implement code scanning in CI/CD pipelines to detect sensitive information; (9) Audit and restrict Git repository access controls.