CVE-2020-15017
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 · uneditedNeDi 1.9C is vulnerable to reflected cross-site scripting. The Devices-Config.php file improperly validates user input. An attacker can exploit this vulnerability by crafting arbitrary JavaScript in the sta GET 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 confidenceNeDi 1.9C contains a reflected cross-site scripting (XSS) vulnerability in Devices-Config.php. The application fails to properly validate user input in the 'sta' GET parameter, allowing attackers to inject arbitrary JavaScript that executes in the victim's browser when crafted links are clicked.
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.9cCVSS 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.
-
Confirm NeDi installationLocate the NeDi application installation directory on the web server. Common paths include /var/www/html/nedi, /opt/nedi, or C:\xampp\htdocs\nedi. Verify that the Devices-Config.php file exists within the html or web-facing directory.Affected if The Devices-Config.php file is present in the web-accessible directory.
-
Identify NeDi versionAccess the NeDi web interface and navigate to the version information page, typically found under Help > System Info, or check the footer of any page for the version number. Alternatively, inspect the version.php or README file in the installation directory.Affected if The installed version is Nedi 1.9C.
-
Verify vulnerable parameter is accessibleLocate the Devices-Config.php file in the installation directory and confirm the application processes the 'sta' GET parameter. This can be done by reviewing the source code for $_GET['sta'] or $_REQUEST['sta'] usage, or by attempting to access the URL pattern: /Devices-Config.php?sta=testAffected if The 'sta' parameter is processed by Devices-Config.php without sanitization.
-
Test for XSS vulnerabilitySubmit a simple test payload in the 'sta' parameter such as: /Devices-Config.php?sta=<script>alert(1)</script>. If the payload is reflected back unescaped in the HTML response, the vulnerability is present.Affected if User-supplied input in the 'sta' parameter is reflected in the response without HTML encoding.
You are affected if NeDi version 1.9C is installed and the Devices-Config.php script reflects the 'sta' parameter input back to the browser without proper sanitization.
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 dataImplement proper input validation and output encoding for the sta parameter. Use context-appropriate escaping when reflecting user input back to the browser, and consider implementing Content Security Policy headers as defense-in-depth.
- 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-2020-15017 — 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-2020-15017 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