CVE-2024-27684
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 · uneditedA Cross-site scripting (XSS) vulnerability in dlapn.cgi, dldongle.cgi, dlcfg.cgi, fwup.cgi and seama.cgi in D-Link GORTAC750_A1_FW_v101b03 allows remote attackers to inject arbitrary web script or HTML via the url parameter.
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 confidenceA reflected XSS vulnerability exists in multiple CGI scripts (dlapn.cgi, dldongle.cgi, dlcfg.cgi, fwup.cgi, seama.cgi) in D-Link GORTAC750_A1_FW_v101b03 firmware. The url parameter in these scripts does not properly sanitize or validate user-supplied input, allowing remote attackers to inject arbitrary JavaScript or HTML that executes in the context of the victim's browser.
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= 101b03CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify firmware version is 101b03Access the device's web administration interface and navigate to the Status or System Information page to view the firmware version. Alternatively, check the device label or documentation for the firmware version string.Affected if The firmware version displayed equals 101b03 exactly.
-
Confirm CGI scripts are accessibleAttempt to access the vulnerable CGI endpoints via HTTP GET request to URLs such as: http://[device-ip]/cgi-bin/dlapn.cgi?url=test, http://[device-ip]/cgi-bin/dldongle.cgi?url=test, http://[device-ip]/cgi-bin/dlcfg.cgi?url=test, http://[device-ip]/cgi-bin/fwup.cgi?url=test, http://[device-ip]/cgi-bin/seama.cgi?url=testAffected if Any of these CGI scripts respond with a page that includes the supplied url parameter value in the response body.
-
Test for reflected XSS in url parameterSend a benign XSS test payload in the url parameter such as: http://[device-ip]/cgi-bin/dlapn.cgi?url=%3Cscript%3Ealert(1)%3C/script%3E and observe whether the script tags are reflected unescaped in the response.Affected if The response body contains the literal string <script>alert(1)</script> or the script executes in the browser context without encoding or sanitization.
If the device runs firmware version 101b03 and the CGI scripts reflect the url parameter input without sanitization, the environment is affected by this CVE.
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 a firmware update when available from D-Link. As a compensating control, disable or restrict access to these CGI endpoints if not required for operation, and implement web application firewall rules to detect and block malicious url parameter payloads.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27684 — 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-2024-27684 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