CVE-2025-30123
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 ROADCAM X3 devices. The mobile app APK (Viidure) contains hardcoded FTP credentials for the FTPX user account, enabling attackers to gain unauthorized access and extract sensitive recorded footage from the device.
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 Viidure mobile APK for ROADCAM X3 devices contains hardcoded FTP credentials for the FTPX user account embedded in the application code. Attackers can extract these credentials from the APK and use them to authenticate to the device's FTP service, gaining unauthorized access to sensitive recorded footage.
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 if Viidure app is installedOn Android, use a package manager app or run 'adb shell pm list packages | grep -i viidure' to check if the Viidure application is installed on the device.Affected if The package name related to Viidure or ROADCAM X3 is found in installed applications.
-
Obtain the APK and search for hardcoded FTP credentialsExtract the APK from the device (using 'adb pull /data/app/*/base.apk' or similar) or download from an official source, then use 'strings' command or a decompiler to search for the literal string 'FTPX' and any associated password patterns embedded in the binary or configuration files.Affected if Hardcoded FTP credentials for user 'FTPX' are found embedded in the APK code or resources.
-
Verify FTP service availability on the deviceCheck if the ROADCAM X3 device has its FTP service exposed on the network. Attempt to resolve the device's IP address or hostname, then test FTP port connectivity (typically port 21) using 'nc -zv <device_ip> 21' or 'telnet <device_ip> 21'.Affected if The device FTP service port is open and reachable on the network.
-
Test authentication with extracted credentialsUsing the credentials found in step 2, attempt to authenticate to the device's FTP service using 'ftp <device_ip>' and entering the extracted username 'FTPX' with its password, or use an FTP client with the extracted credentials.Affected if The FTP server accepts authentication with the hardcoded 'FTPX' credentials, granting access to recorded footage.
A user is affected if the Viidure mobile APK for ROADCAM X3 is installed and the device FTP service is accessible using the hardcoded 'FTPX' credentials extracted from the APK.
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 dataRemove hardcoded credentials from the APK and implement proper credential management (e.g., per-device unique credentials, secure storage, or token-based authentication) for the FTP service, then update both the mobile application and device firmware.
- Consultation3.0 h
- Implementation8.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 $4,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30123 — 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-30123 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