CVE-2025-50123
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 CWE-94: Improper Control of Generation of Code ('Code Injection') vulnerability exists that could cause remote command execution by a privileged account when the server is accessed via a console and through exploitation of the hostname input.
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 confidenceCWE-94 code injection vulnerability in the hostname input field that allows remote command execution when the server is accessed via console by a privileged account.
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
- Physical
- Complexity
- Low
- Privileges
- High
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:P/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Identify products with console hostname configurationSearch your environment for software or services that provide a console interface with hostname input fields. Review installed applications, network management tools, or system configuration interfaces that accept hostname values.Affected if Your environment runs any product that exposes hostname input through a console interface accessible to privileged users
-
Check if console access is enabledExamine system configurations, service settings, and access controls to determine whether console or administrative interface access is enabled. Look for services like IPMI, SOL, ILO, iDRAC, or similar out-of-band management interfaces that may have hostname configuration capabilities.Affected if Console or administrative interfaces with hostname configuration are enabled and reachable on your network
-
Identify privileged account access to consoleReview user account permissions and role assignments to determine which accounts have console or administrative access. Check for accounts with elevated privileges that can access systems via console.Affected if Privileged or administrative accounts exist with console access capabilities to systems with hostname input fields
-
Inspect hostname input configurationExamine configuration files, web interfaces, or CLI tools where hostname values are entered. Look for the specific input field that accepts hostname data and review how the value is processed.Affected if Your system contains a hostname input field in a console or administrative interface that processes the input without strict validation
-
Review logs for suspicious hostname entriesSearch system logs, audit logs, and application logs for unusual or unexpected hostname values that may indicate injection attempts. Look for command syntax, special characters, or code-like patterns in hostname fields.Affected if Logs show anomalous hostname entries containing shell metacharacters, code syntax, or unexpected command patterns
You are affected if your environment runs any software with a console-based hostname input field that is accessible to privileged accounts without strict input validation on that field.
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 input validation and sanitization on hostname input fields, apply the principle of least privilege for console access, and restrict console access to authorized personnel only.
- Consultation2.0 h
- Implementation8.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50123 — 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-50123 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