CVE-2025-61481
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 · uneditedAn issue in MikroTik RouterOS v.7.14.2 and SwOS v.2.18 exposes the WebFig management interface over cleartext HTTP by default, allowing an on-path attacker to execute injected JavaScript in the administrator’s browser and intercept credentials.
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 confidenceMikroTik RouterOS 7.14.2 and SwOS 2.18 expose the WebFig web management interface over unencrypted HTTP by default. An on-path (man-in-the-middle) attacker can inject malicious JavaScript into the administrator's browser session, enabling session hijacking and credential theft.
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
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
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 HTTP service is enabled for WebFigRun '/ip service print' in RouterOS CLI or check IP > Services in Winbox. Look for 'www' service (port 80) enabled.Affected if The 'www' service (HTTP on port 80) is enabled and accessible
-
Check if HTTPS is enforced for WebFigIn WebFig, navigate to System > WebFig or IP > Services. Verify if the service is configured to require HTTPS or if cleartext HTTP is still accepted.Affected if HTTP (port 80) accepts connections without redirecting to HTTPS
-
Confirm WebFig accessibility over HTTPAttempt to access http://[router-ip] from a client on the network. If the login page loads over cleartext HTTP, the interface is exposed.Affected if The WebFig login page loads over cleartext HTTP (not HTTPS)
-
Check SwOS HTTP configuration (for switches)If using SwOS (MikroTik switch operating system), access the switch web interface and check if HTTP access is enabled in the switching settings.Affected if SwOS web interface is accessible over HTTP
If the WebFig management interface is reachable over cleartext HTTP (port 80), the device is affected by this vulnerability and susceptible to man-in-the-middle XSS attacks.
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.
dbcve · scopedEnable HTTPS for WebFig in the MikroTik configuration, disable HTTP access, or restrict management to trusted networks only. Apply any vendor patches if available.
RouterOS 7.15 or later (which includes improved HTTPS defaults and security settings)
- 1. Log in to the MikroTik router via Winbox or SSH using admin credentials
- 2. Navigate to IP > Services or /ip service print to view available management services
- 3. Enable the 'www-ssl' service (HTTPS) and configure a valid certificate: /ip service set www-ssl certificate=<your-certificate>
- 4. Disable the insecure 'www' service (HTTP) to prevent cleartext access: /ip service disable www
- 5. Alternatively, if www-ssl is not available, upgrade RouterOS to a version that supports SSL services
- 6. Verify that only HTTPS (port 443) is accessible for WebFig and HTTP (port 80) returns no response
- 7. Ensure the SSL certificate is valid and properly configured under System > Certificates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61481 — 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-61481 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