CVE-2019-14703
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 CSRF issue was discovered in webparam?user&action=set¶m=add in HTTPD on MicroDigital N-series cameras with firmware through 6400.0.8.5 to create an admin account.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in MicroDigital N-series camera firmware allows remote attackers to create unauthorized admin accounts by tricking authenticated users into submitting malicious requests to the webparam endpoint with parameters user, action=set, and param=add.
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<= 6400.0.8.5<= 6400.0.8.5<= 6400.0.8.5CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 camera modelAccess the camera web interface or check the device label/documentation to confirm the exact model number (Mdc N4090, Mdc N4090w, or Mdc N2190v)Affected if The model is NOT one of these three listed models - you are not affected by this specific CVE
-
Check the installed firmware versionLog into the camera admin interface and navigate to System > Firmware or System > Information to view the firmware version, or use the ONVIF/SNMP interface if availableAffected if The firmware version is greater than 6400.0.8.5 - you are not affected; if <= 6400.0.8.5 or version cannot be determined, you may be affected
-
Verify the web interface is accessibleAttempt to access the camera web interface via HTTP/HTTPS on the standard ports (typically 80, 8080, or 443)Affected if The web interface is not exposed to the network (only accessible locally), the attack surface is reduced but the vulnerability still exists in the firmware
-
Confirm the webparam endpoint existsAccess the URL path /cgi-bin/webparam or /webparam directly in a browser while logged in as admin to verify the endpoint respondsAffected if The endpoint returns an error or is not found, the specific CSRF vector may not be present but the underlying firmware vulnerability may still exist
-
Check for anti-CSRF protection on user managementExamine the HTML source of the camera admin user management page to look for hidden CSRF tokens in forms, or attempt a benign user add operation and inspect the request/response for token usageAffected if No anti-CSRF tokens are present in user management forms, the camera is vulnerable to the described attack
You are affected if you have a MicroDigital Mdc N4090, N4090w, or N2190v camera running firmware version 6400.0.8.5 or lower, with the web interface accessible either locally or remotely.
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 dataImplement anti-CSRF tokens in all state-changing operations (especially user management) and verify the Origin/Referer headers server-side. For immediate workarounds, administrators should avoid browsing untrusted sites while logged into the camera admin interface.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14703 — 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-2019-14703 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