CVE-2025-2350
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 · uneditedA vulnerability was found in IROAD Dash Cam FX2 up to 20250308. It has been rated as critical. Affected by this issue is some unknown functionality of the file /action/upload_file. The manipulation leads to unrestricted upload. Access to the local network is required for this attack to succeed. The exploit has been disclosed to the public and may be used.
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 Dash Cam FX2 device has an unrestricted file upload vulnerability in the /action/upload_file endpoint, allowing an attacker with local network access to upload arbitrary files to the device. This could enable remote code execution or complete device compromise.
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 data<= 2025-03-08CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 on your networkLocate the IROAD Dash Cam FX2 device IP address by checking your router's connected devices list or scanning your local network for web servers on common ports (80, 8080, 443). The device typically runs a web interface for configuration.Affected if The device is accessible on your local network and responds on HTTP/HTTPS ports.
-
Check the installed firmware versionAccess the device web interface through its IP address and navigate to the Settings or System Information page. Look for a firmware version field or build date. Alternatively, check the vendor mobile app if used for device management.Affected if The firmware version or build date is on or before 2025-03-08.
-
Verify the vulnerable endpoint existsSend an HTTP GET or POST request to http://[DEVICE_IP]/action/upload_file using a tool like curl or a browser. Observe whether the endpoint responds (even with an error message).Affected if The endpoint responds with any HTTP status code, indicating the upload functionality is present.
-
Test endpoint accessibility without credentialsAttempt to access the /action/upload_file endpoint directly without providing any authentication cookies, tokens, or credentials. Use curl -X POST http://[DEVICE_IP]/action/upload_file to probe the endpoint.Affected if The endpoint accepts requests without requiring authentication.
Your device is affected if it is an IROAD Dash Cam FX2 running firmware dated 2025-03-08 or earlier, with the /action/upload_file endpoint accessible on your network without authentication.
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 dataRestrict network access to the device, implement file type validation and authentication on the upload endpoint, and apply any available firmware updates from the vendor.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2350 — 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-2350 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