CVE-2013-2560
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 · uneditedDirectory traversal vulnerability in the web interface on Foscam devices with firmware before 11.37.2.49 allows remote attackers to read arbitrary files via a .. (dot dot) in the URI, as demonstrated by discovering (1) web credentials or (2) Wi-Fi credentials.
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 confidenceDirectory traversal vulnerability in Foscam IP camera web interfaces allows remote attackers to access arbitrary files on the device filesystem using '../' sequences in the URI. The vulnerability enables exposure of sensitive configuration files containing web and Wi-Fi credentials.
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<= firmware_11.37.2.47CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/I:N/A:N
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.
-
Confirm device model is Fi8919wAccess the camera web interface or check the device label/sticker to verify the model number is Fi8919wAffected if Device is not a Foscam Fi8919w model - this specific vulnerability only applies to that model
-
Check installed firmware versionLog into the camera web interface and navigate to the device settings or system information page to view the firmware version. Alternatively, check Foscam configuration files or use the camera's API if available.Affected if Firmware version is 11.37.2.47 or lower, or if the version cannot be determined but the device is confirmed as Fi8919w
-
Verify web interface is accessibleAttempt to access the camera web interface from a browser using the device IP address (e.g., http://<camera_ip>/). Confirm the interface is reachable.Affected if Web interface is accessible over the network - the directory traversal vulnerability can only be exploited if the web interface is reachable
-
Check network exposure of the web interfaceDetermine if the camera web interface is exposed to untrusted networks by reviewing router port forwarding rules, firewall configurations, or NAT settings that may allow external access to the camera's IP and web port.Affected if Web interface is exposed to the internet or untrusted networks - this increases the likelihood of remote exploitation
A user is affected if they have a Foscam Fi8919w camera with firmware version 11.37.2.47 or lower and the web interface is accessible on the network.
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 dataUpdate Foscam firmware to version 11.37.2.49 or later to patch the path traversal vulnerability. If patching is not immediately possible, restrict web interface access to trusted networks or disable remote web access.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2560 — 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-2560 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