CVE-2013-3963
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 goform/usermanage in Grandstream GXV3501, GXV3504, GXV3601, GXV3601HD/LL, GXV3611HD/LL, GXV3615W/P, GXV3651FHD, GXV3662HD, GXV3615WP_HD, GXV3500, and possibly other camera models allows remote attackers to hijack the authentication of unspecified victims for requests that add users.
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 the goform/usermanage endpoint of Grandstream IP camera web interfaces allows remote attackers to inject unauthorized users by tricking authenticated administrators into visiting malicious sites. The attack exploits the lack of anti-CSRF tokens in user management requests.
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<= 1.0.4.43= 1.0.2.3= 1.0.3.9= 1.0.4.6= 1.0.4.7= 1.0.4.11= 1.0.4.16= 1.0.4.27= 1.0.4.34= 1.0.4.37= 1.0.4.38= 1.0.4.39all versionsall versionsall versionsall versionsall versionsall versionsall 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 the device modelAccess the device web interface or check the device label/documentation to confirm it is a Grandstream Gxv series IP camera (e.g., Gxv3500, Gxv3501, Gxv3504, Gxv3601, Gxv3601hd/ll, Gxv3611hd/ll, Gxv3615w/p)Affected if The device is a Grandstream Gxv series IP camera listed in the affected products
-
Check the firmware versionLog into the device web interface and navigate to the status or system information page to view the installed firmware version. Compare this version number against the affected ranges: <= 1.0.4.43, or exactly 1.0.2.3, 1.0.3.9, 1.0.4.6, 1.0.4.7, 1.0.4.11, 1.0.4.16, 1.0.4.27, 1.0.4.34, 1.0.4.37, 1.0.4.38, or 1.0.4.39Affected if The installed firmware version matches any of the listed affected versions
-
Confirm device falls under 'all versions' categoryFor models Gxv3500, Gxv3501, Gxv3504, Gxv3601, Gxv3601hd/ll, Gxv3611hd/ll, or Gxv3615w/p, note that all firmware versions are affected regardless of version numberAffected if The device model is any Gxv3500, Gxv3501, Gxv3504, Gxv3601, Gxv3601hd/ll, Gxv3611hd/ll, or Gxv3615w/p
-
Verify web interface accessibilityAttempt to access the device web interface over HTTP/HTTPS on the typical ports (80/443 or custom port). Confirm the goform/usermanage endpoint is reachable (e.g., by accessing the user management page)Affected if The device web interface is accessible from a network where attackers could trick an authenticated administrator into visiting malicious sites
A user is affected if they operate any Grandstream Gxv series IP camera with firmware matching the affected versions, or any of the Gxv3500/3501/3504/3601/3601hd/ll/3611hd/ll/3615w/p models at any firmware version, and the device web interface is network-accessible to potential attackers.
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 dataApply vendor firmware updates if available; until then, restrict administrative access to trusted networks only and use browser anti-CSRF extensions. Network segmentation can limit exposure.
- Consultation6.0 h
- Implementation12.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 $6,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3963 — 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-3963 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