CVE-2025-30133
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 was discovered on IROAD Dashcam FX2 devices. Bypass of Device Pairing/Registration can occur. It requires device registration via the "IROAD X View" app for authentication, but its HTTP server lacks this restriction. Once connected to the dashcam's Wi-Fi network via the default password ("qwertyuiop"), an attacker can directly access the HTTP server at http://192.168.10.1 without undergoing the pairing process. Additionally, no alert is triggered on the device when an attacker connects, making this intrusion completely silent.
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 confidenceThe IROAD Dashcam FX2 has an authentication bypass vulnerability where the embedded HTTP server does not enforce the device pairing/registration requirement that the mobile app enforces. An attacker who connects to the dashcam's Wi-Fi network using the default weak password ('qwertyuiop') can directly access http://192.168.10.1 without completing the app-based pairing process, allowing unauthenticated access to the device's HTTP interface.
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 dataall versionsCVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify IROAD FX2 dashcam on networkScan the network for devices responding at 192.168.10.1 or look for Wi-Fi SSIDs containing 'IROAD' or 'FX2'Affected if A device at 192.168.10.1 is identified as an IROAD dashcam or a dashcam Wi-Fi network is visible
-
Verify Wi-Fi uses default weak passwordCheck if the dashcam Wi-Fi network (typically IROAD_XXXX or similar) is using the default password 'qwertyuiop'Affected if The dashcam Wi-Fi is accessible using the password 'qwertyuiop'
-
Test HTTP interface access without pairingConnect to the dashcam Wi-Fi network and navigate to http://192.168.10.1 in a browser without completing any mobile app pairing processAffected if The HTTP interface loads and displays device controls or settings without requiring authentication or app pairing completion
-
Confirm no authentication enforcement on endpointsTry accessing different HTTP endpoints (such as /settings, /live, /record) on 192.168.10.1 without any credentialsAffected if Any endpoint returns device data, configuration, or control options without requiring authentication
A user is affected if they have an IROAD FX2 dashcam accessible via Wi-Fi using the default password 'qwertyuiop' where the HTTP interface at 192.168.10.1 is reachable without completing the app-based pairing process.
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 dataImmediately change the default Wi-Fi password from 'qwertyuiop' to a strong, unique password. Isolate the dashcam on a dedicated network segment (VLAN) to limit exposure. Contact IROAD for a firmware update that enforces authentication on the HTTP server.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30133 — 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-30133 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