dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Apr 2022.
Dsl 2760u FirmwareOperating system · Dlink

CVE-2013-5223

MEDIUM · 5.4 CVSS v3.1 Published 2013-11-19
Fix available
A fix is available. Upgrade to 1.12 or later.
See remediation →
98/100
Remediation priority · Urgent
In the wild Public exploit Remotely reachable

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 · unedited
Multiple cross-site scripting (XSS) vulnerabilities in D-Link DSL-2760U Gateway (Rev. E1) allow remote authenticated users to inject arbitrary web script or HTML via the (1) ntpServer1 parameter to sntpcfg.cgi, username parameter to (2) ddnsmngr.cmd or (3) todmngr.tod, (4) TodUrlAdd parameter to urlfilter.cmd, (5) appName parameter to scprttrg.cmd, (6) fltName in an add action or (7) rmLst parameter in a remove action to scoutflt.cmd, (8) groupName parameter to portmapcfg.cmd, (9) snmpRoCommunity parameter to snmpconfig.cgi, (10) fltName parameter to scinflt.cmd, (11) PolicyName in an add action or (12) rmLst parameter in a remove action to prmngr.cmd, (13) ippName parameter to ippcfg.cmd, (14) smbNetBiosName or (15) smbDirName parameter to samba.cgi, or (16) wlSsid parameter to wlcfg.wl.

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 confidence

D-Link DSL-2760U Gateway Rev. E1 web interface contains 16 reflected XSS vulnerabilities in multiple CGI endpoints. Authenticated attackers can inject arbitrary JavaScript/HTML through parameters including ntpServer1, username, TodUrlAdd, fltName, groupName, snmpRoCommunity, PolicyName, ippName, smbNetBiosName, smbDirName, and wlSsid across various .cgi and .cmd handlers.

MitigationApply vendor firmware update if available; otherwise implement input validation with strict allowlist filtering and output encoding for all user-supplied parameters in the affected CGI scripts.

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
Dsl 2760u FirmwareOperating system
Affected:< 1.12

CVSS 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and hardware revision
    Check the device label or access the web interface and look for the model number DSL-2760U and hardware revision E1 in the status or device info page
    Affected if The device is a D-Link DSL-2760U Gateway Rev. E1
  2. Check installed firmware version
    Access the router web interface, navigate to the firmware or status page, and note the firmware version number displayed
    Affected if The firmware version is less than 1.12 (for example, 1.10, 1.11, or any version number below 1.12)
  3. Verify web interface accessibility
    Attempt to access the router web interface by entering the router IP address in a web browser
    Affected if The web interface is reachable and responds to HTTP/HTTPS requests
  4. Check if authentication is possible
    Attempt to log into the web interface using valid or default administrator credentials
    Affected if You can authenticate to the web interface (valid credentials or known default credentials work)

You are affected if you have a D-Link DSL-2760U Rev. E1 device running firmware version 1.12 or lower, with the web interface accessible and you have administrative access to the device.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.12 or later
Fixed in 1.12
Interim mitigation

Apply vendor firmware update if available; otherwise implement input validation with strict allowlist filtering and output encoding for all user-supplied parameters in the affected CGI scripts.

Recommended fix Moderate confidence

D-Link DSL-2760U (Rev. E1) firmware version 1.12 or later

  1. 1. Identify the current firmware version of the D-Link DSL-2760U (Rev. E1) device by accessing the web administration interface
  2. 2. Navigate to the firmware update or system settings section in the router's web UI
  3. 3. Download the latest firmware version 1.12 or later from the official D-Link support website (support.dlink.com)
  4. 4. Upload and apply the firmware file through the router's web interface or using the firmware upgrade tool if available
  5. 5. After the upgrade completes, verify the new firmware version is installed and test that the device functions normally
  6. 6. Confirm the vulnerability is remediated by verifying the affected CGI endpoints (sntpcfg.cgi, ddnsmngr.cmd, todmngr.tod, urlfilter.cmd, scprttrg.cmd, scoutflt.cmd, portmapcfg.cmd, snmpconfig.cgi, scinflt.cmd, prmngr.cmd, ippcfg.cmd, samba.cgi, wlcfg.wl) no longer accept unsanitized input
Caveat Firmware upgrades may temporarily disrupt network connectivity; ensure backup of configuration; some settings may reset to defaults requiring reconfiguration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dsl 2760u Firmware Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-5223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-5223 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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