CVE-2013-0144
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 · uneditedCross-site request forgery (CSRF) vulnerability in cgi-bin/create_user.cgi on QNAP VioStor NVR devices with firmware 4.0.3 allows remote attackers to hijack the authentication of administrators for requests that create administrative accounts via a NEW USER action.
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 confidenceCSRF vulnerability in QNAP VioStor NVR firmware 4.0.3's create_user.cgi script allows remote attackers to inject administrative accounts by tricking authenticated administrators into visiting malicious pages, hijacking their session authentication.
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= 4.0.3all 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 QNAP VioStor NVR systemAccess the device admin web interface or check system information via SSH. Look for 'VioStor' or 'QNAP' branding in the web interface or system banner.Affected if The system is not a QNAP VioStor NVR device, then it is not affected by this specific CVE.
-
Check firmware versionIn the web interface, go to System Administration > System Settings > Firmware Version, or run 'versus' command via SSH if available. Look for exact version number 4.0.3.Affected if The firmware version is exactly 4.0.3 - this version is confirmed affected.
-
Verify create_user.cgi endpoint existsAccess the web interface and confirm the user management CGI script is present at the typical path /cgi-bin/create_user.cgi or similar user creation endpoint.Affected if The create_user.cgi script exists and is accessible without additional CSRF protection - this is the vulnerable component.
-
Check for anti-CSRF protectionInspect the create_user.cgi page source or form submissions for presence of anti-CSRF tokens or SameSite cookie attributes. Submit a test request without a token to see if it succeeds.Affected if No anti-CSRF token is required and the request succeeds without authentication tokens - the vulnerability is exploitable.
A user is affected if they are running QNAP VioStor NVR firmware exactly version 4.0.3 with the create_user.cgi script accessible and lacking CSRF token validation.
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 dataUpgrade QNAP VioStor NVR firmware to a version beyond 4.0.3 that includes CSRF token validation in create_user.cgi; implement SameSite cookies and anti-CSRF tokens as defense-in-depth.
- Consultation3.0 h
- Implementation2.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 $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0144 — 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-2013-0144 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