CVE-2020-15030
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 cross-site scripting (XSS) attack. The application allows an attacker to execute arbitrary JavaScript code via the Topology-Routes.php rtr 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 Topology-Routes.php where the 'rtr' parameter is not properly sanitized before being reflected in the HTML output, allowing an attacker to inject arbitrary JavaScript code through a malicious URL.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm NeDi installation and versionLocate the NeDi installation directory and check the version. Look for version files such as 'Version.pm' in the lib directory, or check the main index/login page which often displays the version. Common install paths include /var/www/html/nedi or C:\xampp\htdocs\nedi on Windows.Affected if The installed version is NeDi 1.9C exactly.
-
Verify Topology-Routes.php existsNavigate to the NeDi web root directory and locate the Topology-Routes.php file. This file is typically found in the /php directory or directly in the web root depending on the installation. Confirm the file is present on the system.Affected if The file Topology-Routes.php exists in the NeDi installation directory.
-
Check if the 'rtr' parameter is processed unsafelyExamine the Topology-Routes.php source code and look for how the 'rtr' parameter is handled. Search for code that retrieves the 'rtr' parameter (e.g., using $_GET['rtr'] or $_REQUEST['rtr']) and directly outputs it into HTML without using htmlspecialchars() or equivalent encoding functions.Affected if The code retrieves the 'rtr' parameter and reflects it into HTML output without proper sanitization or encoding.
-
Test for XSS via URL parameterAccess the Topology-Routes.php page through the web browser and attempt to inject a test XSS payload into the 'rtr' parameter, such as: Topology-Routes.php?rtr=<script>alert('XSS')</script>. If the payload executes or is reflected as-is in the response without being encoded, the vulnerability is present.Affected if The 'rtr' parameter value is reflected in the HTML response without encoding or sanitization.
You are affected if you are running NeDi version 1.9C with the Topology-Routes.php file present and the 'rtr' parameter is being reflected in HTML output without proper sanitization or encoding.
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 proper input validation and output encoding/escaping for the 'rtr' parameter in Topology-Routes.php to neutralize malicious script content.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15030 — 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-15030 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