CVE-2025-50121
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-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability exists that could cause unauthenticated remote code execution when a malicious folder is created over the web interface HTTP when enabled. HTTP is disabled by default.
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 confidenceA CWE-78 OS Command Injection vulnerability in the web interface allows unauthenticated remote code execution through creation of a maliciously crafted folder name when HTTP is enabled. The vulnerability has a CVSS score of 9.5 (Critical).
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
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/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.
-
Verify if HTTP web interface is enabledAccess the device admin console or check configuration settings for HTTP/HTTPS web interface status. On most network devices, this is found in System Settings > Management > Web Interface or similar. For CLI-based checks, look for commands like 'show http server' or 'show web-management'.Affected if HTTP web interface is in ENABLED state (the vulnerability only applies when the interface is active)
-
Identify the installed software versionCheck the product firmware or software version through the admin interface (usually displayed on the dashboard or in System Information), or via CLI command such as 'show version', 'firmware version', or similar device-specific command.Affected if Version cannot be determined or is unknown (you cannot verify if it falls within any patched range)
-
Compare your version against vendor release notesReview the vendor's security advisory for CVE-2025-50121 to obtain the specific fixed version numbers, then compare against your installed version identified in step 2.Affected if Your version is older than the fixed version listed in vendor documentation, or no fix version is documented for your product line
-
Inspect for unexpected folders in web rootIf you have CLI or filesystem access, navigate to the web server document root (commonly /www, /htdocs, /web, or device-specific paths) and list all directories. Look for unfamiliar or recently created folder names that you did not create.Affected if Unknown folders or directories exist in the web interface filesystem that you did not create
You are affected if the HTTP web interface is enabled AND your installed version is older than the vendor-fixed version, or if you find unexpected folders in the web directory indicating possible exploitation.
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 dataDisable HTTP if not required (it is disabled by default). If HTTP is needed, apply vendor-provided patches immediately and implement strict input validation for folder creation parameters.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50121 — 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-50121 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