dbcve.org
RouterosOperating system · Mikrotik

CVE-2023-30799

HIGH · 7.2 CVSS v3.1 Published 2023-07-19
Fix available
A fix is available. Upgrade to 6.49.7 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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
MikroTik RouterOS stable before 6.49.7 and long-term through 6.48.6 are vulnerable to a privilege escalation issue. A remote and authenticated attacker can escalate privileges from admin to super-admin on the Winbox or HTTP interface. The attacker can abuse this vulnerability to execute arbitrary code on the system.

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 confidence

MikroTik RouterOS contains a privilege escalation vulnerability allowing a remote authenticated attacker with standard admin access to escalate to super-admin privileges through the Winbox or HTTP interface. This enables arbitrary code execution on affected devices running stable versions before 6.49.7 or long-term versions through 6.48.6.

MitigationUpgrade MikroTik RouterOS to version 6.49.7 or later (stable) or 6.48.7 or later (long-term) to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RouterosOperating system
Affected:<= 6.48.7>= 6.34, < 6.49.7

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Determine RouterOS version
    Log into the router via console, SSH, or Winbox and run the command: /system resource print or /system package print. Locate the version field in the output.
    Affected if The installed version is 6.34 or higher but lower than 6.49.7 (stable) or lower than 6.48.7 (long-term)
  2. Identify the specific RouterOS release track
    In the version output, determine whether the installation is a stable (main) release or a long-term release by checking the release notes or the version string format.
    Affected if The version is a long-term release at 6.48.6 or below, or a stable release below 6.49.7
  3. Check if Winbox interface is accessible
    Run /ip service print and review whether the winbox service is enabled and on which address it is bound. Optionally scan TCP port 8291 from an external host.
    Affected if Winbox service (TCP port 8291) is enabled and reachable by an authenticated admin user
  4. Check if HTTP or HTTPS interface is accessible
    Run /ip service print to verify if www or www-ssl services are enabled. Optionally attempt to access the web interface on ports 80 or 443.
    Affected if HTTP (port 80) or HTTPS (port 443) interface is enabled and reachable by an authenticated admin user

The environment is affected if RouterOS version falls within 6.34 to 6.48.7 for long-term or 6.34 to 6.49.7 for stable releases AND either the Winbox or HTTP administrative interface is accessible to a standard admin account.

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.

dbcve · scoped
Upgrade available Upgrade to 6.49.7 or later
Fixed in 6.49.7
Interim mitigation

Upgrade MikroTik RouterOS to version 6.49.7 or later (stable) or 6.48.7 or later (long-term) to remediate this vulnerability.

Recommended fix High confidence

RouterOS 6.49.7 (stable) or later, or the latest long-term release branch

  1. 1. Backup the current RouterOS configuration using the /export command or via Winbox/HTTP interface
  2. 2. Download RouterOS version 6.49.7 or later (stable) from the MikroTik download page
  3. 3. Upload the new RouterOS .npk file via Winbox, HTTP, or FTP to the router
  4. 4. Reboot the router to apply the upgrade
  5. 5. After reboot, verify the RouterOS version shows 6.49.7 or later using the /system resource print command
  6. 6. Verify the configuration is intact and test critical services
  7. 7. As a precaution, change admin passwords after the upgrade
Caveat MikroTik minor version upgrades are generally low-risk but always backup configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Routeros Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,730
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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