D-Link DCS cameras have a weak/insecure CrossDomain.XML file that allows sites hosting malicious Flash objects to access and/or change the d
D-Link DCS cameras have a weak/insecure CrossDomain.XML file that allows sites hosting malicious Flash objects to access and/or change the device's settings via a CSRF attack. This is because of the 'allow-access-from domain' child element set to *, thus accepting requests from any domain. If a victim logged into the camera's web console visits a malicious site hosting a malicious Flash file from another Browser tab, the malicious Flash file then can send requests to the victim's DCS series Camera without knowing the credentials. An attacker can host a malicious Flash file that can retrieve Live Feeds or information from the victim's DCS series Camera, add new admin users, or make other changes to the device. Known affected devices are DCS-933L with firmware before 1.13.05, DCS-5030L, DCS-5020L, DCS-2530L, DCS-2630L, DCS-930L, DCS-932L, and DCS-932LB1.
- Published
- Apr 24, 2017
- Updated
- Jun 16, 2026
- EPSS
- 4.3% · 91th percentile
- CWE
- CWE-352
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| dlink | dcs-2230l firmware | cpe:2.3:o:dlink:dcs-2230l_firmware |
| dlink | dcs-2230l | cpe:2.3:h:dlink:dcs-2230l |
| dlink | dcs-2310l firmware | cpe:2.3:o:dlink:dcs-2310l_firmware |
| dlink | dcs-2310l | cpe:2.3:h:dlink:dcs-2310l |
| dlink | dcs-2332l firmware | cpe:2.3:o:dlink:dcs-2332l_firmware |
| dlink | dcs-2332l | cpe:2.3:h:dlink:dcs-2332l |
| dlink | dcs-6010l firmware | cpe:2.3:o:dlink:dcs-6010l_firmware |
| dlink | dcs-6010l | cpe:2.3:h:dlink:dcs-6010l |
| dlink | dcs-7010l firmware | cpe:2.3:o:dlink:dcs-7010l_firmware |
| dlink | dcs-7010l | cpe:2.3:h:dlink:dcs-7010l |
| dlink | dcs-2530l firmware | cpe:2.3:o:dlink:dcs-2530l_firmware |
| dlink | dcs-2530l | cpe:2.3:h:dlink:dcs-2530l |
and 40 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dlink dcs-2132l firmwareup to 2.12.00 inclusive
- dlink dcs-2132l firmwareup to 1.08.01 inclusive
- dlink dcs-2136l firmwareup to 1.04.01 inclusive
- dlink dcs-2210l firmwareup to 1.03.01 inclusive
- dlink dcs-2230l firmwareup to 1.03.01 inclusive
- dlink dcs-2310l firmwareup to 2.03.00 inclusive
- dlink dcs-2310l firmwareup to 1.08.01 inclusive
- dlink dcs-2330l firmwareup to 1.13.00 inclusive
- dlink dcs-2332l firmwareup to 1.08.01 inclusive
- dlink dcs-2530l firmwareup to 1.00.21 inclusive
- dlink dcs-5000l firmwareup to 1.02.02 inclusive
- dlink dcs-5009l firmwareup to 1.07.05 inclusive
- dlink dcs-5010l firmwareup to 1.13.05 inclusive
- dlink dcs-5020l firmwareup to 1.13.05 inclusive
- dlink dcs-5025l firmwareup to 1.02.10 inclusive
- dlink dcs-5029l firmwareup to 1.12.00 inclusive
- dlink dcs-5030l firmwareup to 1.01.06 inclusive
- dlink dcs-5222l firmwareup to 2.12.00 inclusive
- dlink dcs-6010l firmwareup to 1.15.01 inclusive
- dlink dcs-6212l firmwareup to 1.00.12 inclusive
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2017-02-22 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-61 d
- Published
- TodaySep 30, 2026+3446 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.