CVE-2025-30125
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 Marbella KR8s Dashcam FF 2.0.8 devices. All dashcams were shipped with the same default credentials of 12345678, which creates an insecure-by-default condition. For users who change their passwords, it's limited to 8 characters. These short passwords can be cracked in 8 hours via low-end commercial cloud resources.
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 Marbella KR8s Dashcam FF 2.0.8 ships with a hardcoded default password '12345678' for all devices, creating a critical insecure-by-default condition. Additionally, user-chosen passwords are limited to only 8 characters, which can be brute-forced in approximately 8 hours using low-end commercial cloud computing resources.
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
- 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 the device modelLocate the dashcam in your inventory or network and confirm it is a Marbella KR8s Dashcam FF model. Check the device label, management interface, or DHCP lease logs for the device hostname or manufacturer identifier.Affected if The device is a Marbella KR8s Dashcam FF
-
Check the firmware versionAccess the dashcam administration interface or check the device system information to determine the installed firmware version. Compare this against version 2.0.8.Affected if The firmware version is 2.0.8
-
Test for the hardcoded default passwordAttempt to authenticate to the dashcam web interface or API using the username for the administrator account and the password '12345678'. Note: only perform this on devices you are authorized to test.Affected if Authentication succeeds with the password '12345678'
-
Verify password length limitationAccess the password change or account settings in the dashcam administration interface. Attempt to set a password longer than 8 characters to see if the interface rejects it or truncates it.Affected if The interface rejects or truncates passwords longer than 8 characters
You are affected if you have a Marbella KR8s Dashcam FF running firmware version 2.0.8 that either still uses the default password '12345678' or enforces an 8-character maximum password length.
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 password to a strong, unique credential; if the device firmware cannot support longer passwords, isolate the device on a restricted network segment and contact the vendor for a firmware update that removes the 8-character password limitation.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30125 — 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-30125 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