Router vulnerability note - MikroTik
MikroTik WebFig over cleartext HTTP, by default, in 2025
What happened
The finding is not exotic and the score is: WebFig, the web UI that ships enabled, is reachable over HTTP without forcing the browser to HTTPS. Anyone in the path — the ISP's equipment, a cafĂ© hotspot, the managed switch with the port mirror — can serve JavaScript into your admin session and watch what you type. The CVSS vector earned a 10.0, which happens rarely and mostly to services that are on by default.
Our position on this one is the boring one. If you are configuring a router over HTTP from a laptop on the LAN, the exposure is a person with a laptop in your building. If you are doing it over HTTP from a phone on mobile data because that is how you found the problem, you are the on-path attacker's best friend. And if you leave WebFig exposed on the WAN over HTTP, the 10.0 is not unfair.
Who is affected
RouterOS 7.14.2 and SwOS 2.18 as tested; the behaviour applies to the default configuration of the web interface, not one build.
Check it yourself
What does the lock icon actually mean?
[admin@router] > /ip service print where name~"www"
# NAME PORT ADDRESS CERTIFICATE
7 www 80 0.0.0.0/0 none
8 www-ssl 443 0.0.0.0/0 none
[admin@router] > /ip http print
proxy: none
[admin@router] > /certificate print where name~"mikrotik"
(no certificate is the usual answer)
Do this
- Install a certificate — a real one if the box has a hostname, the self-signed one if it does not.
- Prefer HTTPS in the browser address bar; type it, do not let the browser guess.
- Disable HTTP entirely once you have confirmed the WebUI works over TLS.
- If the device is reachable from the internet, disable HTTP the same day.
How we handle it
Certificates are part of every hardening job we do, and on RouterOS 7 we usually push a Let's Encrypt certificate with a DNS-01 challenge so the box does not need a public port. That is an hour of our time on the tunnel, and it removes a 10.0 from your network.