CVE-2025-9160
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 code execution security issue exists in the affected product. An attacker with physical access could abuse the maintenance menu of the controller with a crafted payload. The security issue can result in arbitrary code execution.
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 confidenceA vulnerability exists in the maintenance menu of a controller device that allows an attacker with physical access to execute arbitrary code via a crafted payload. The specific vulnerability type (e.g., command injection, buffer overflow) is not detailed in the available information.
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
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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 controller device with maintenance menuLocate all controller devices in your environment that include a maintenance or diagnostic menu function. Review device inventory or physically inspect devices for maintenance interface access points.Affected if A controller device with an accessible maintenance menu is present in the environment
-
Verify maintenance menu accessibilityAttempt to access or enumerate the maintenance menu on the controller device through its standard interface (physical console, web UI, or administrative port). Document whether authentication is required and if the menu is enabled by default.Affected if The maintenance menu is accessible without authentication or is enabled by default
-
Assess physical access controlsEvaluate who has physical access to the controller device. Check if the device is located in a secured area, locked cabinet, or restricted facility. Review access logs if available.Affected if The controller device can be accessed by unauthorized or untrusted individuals
-
Check for vendor firmware versionQuery the controller device for its current firmware or software version using vendor-provided commands or interfaces. Compare this version against any vendor advisories or release notes.Affected if The device firmware version predates any vendor patch release for CVE-2025-9160
-
Review maintenance menu configurationExamine the maintenance menu configuration settings via the device administrative interface. Check for options that disable, hide, or password-protect the maintenance function.Affected if The maintenance menu lacks additional authentication or access controls beyond default settings
Your environment is affected if you operate a controller device with a maintenance menu that is accessible to individuals with physical access, and no vendor patch has been applied.
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 dataRestrict physical access to the controller and disable or secure the maintenance menu until a vendor patch is available. If the maintenance menu is necessary, implement additional input validation and authentication controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9160 — 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-9160 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