dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-6892

HIGH · 8.7 CVSS v4.0 Published 2025-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable No privileges

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
An Incorrect Authorization vulnerability has been identified in Moxa’s network security appliances and routers. A flaw in the API authentication mechanism allows unauthorized access to protected API endpoints, including those intended for administrative functions. This vulnerability can be exploited after a legitimate user has logged in, as the system fails to properly validate session context or privilege boundaries. An attacker may leverage this flaw to perform unauthorized privileged operations. While successful exploitation can severely impact the confidentiality, integrity, and availability of the affected device itself, there is no loss of confidentiality or integrity within any subsequent systems.

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 confidence

Moxa network security appliances and routers contain an incorrect authorization vulnerability in their API authentication mechanism. The flaw allows privilege escalation by failing to properly validate session context or privilege boundaries after a legitimate user logs in, enabling unauthorized access to administrative API endpoints.

MitigationApply vendor-supplied firmware updates or patches when available; until then, implement network segmentation and strict access controls to limit exposure to the administrative API interfaces.

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
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Moxa network devices on your network
    Review your network inventory, scan for Moxa MAC OUIs (vendor prefix), or check device labels/web interfaces for 'Moxa' branding. Common product lines include NPort, OnCell, and AWK series devices.
    Affected if Any Moxa network security appliance, router, or serial-to-Ethernet device is present in the environment.
  2. Determine the installed firmware version
    Log into the device web interface or use SNMP to query sysDescr. Navigate to System > Firmware or Status > Device Information. Compare the version number against any Moxa security advisories for CVE-2025-6892.
    Affected if The firmware version matches or predates the versions noted as vulnerable in Moxa's advisory for this CVE.
  3. Verify if the REST API is enabled and accessible
    Attempt to reach the API endpoint (commonly /api/v1 or /rest) over HTTPS on the device's management IP. Check device settings under Network > Services or Administration > API to confirm API access is enabled.
    Affected if The device REST API interface is enabled and responds to unauthenticated or authenticated requests.
  4. Inspect API access logs for privilege escalation indicators
    Export or review API logs from the device (usually via Logs > System Logs or external syslog). Search for sequential API calls showing privilege escalation, unexpected administrative endpoint access, or session anomalies.
    Affected if Logs show unauthorized administrative API calls, unexpected privilege escalation patterns, or sessions accessing endpoints above their assigned permission level.
  5. Review user accounts and session configurations
    Check the device's user management page (Administration > User Accounts) for unexpected administrative accounts. Also review active sessions for legitimacy.
    Affected if Unauthorized administrative accounts exist, or sessions from standard users are observed accessing administrative API functions.

You are affected if you operate any Moxa network security appliance or router with an API interface enabled, where the installed firmware version falls within the vulnerable range or cannot be confirmed as patched.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates or patches when available; until then, implement network segmentation and strict access controls to limit exposure to the administrative API interfaces.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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