CVE-2020-15016
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 Other-Converter.php file improperly validates user input. An attacker can exploit this vulnerability by crafting arbitrary JavaScript in the txt 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 vulnerability in Other-Converter.php. The txt GET parameter is not properly validated, allowing an attacker to inject arbitrary JavaScript via a crafted 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
- 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 installation and versionLocate the NeDi installation directory and check the version. Look for version files (often version.txt, or check the footer/login page of the web interface). Common paths: /var/www/html/nedi, /var/www/nedi, or C:\inetpub\wwwroot\nediAffected if The installed version is exactly 1.9c (the vulnerable version)
-
Verify Other-Converter.php existsCheck for the presence of Other-Converter.php in the NeDi web directory. Search for the file at paths like /var/www/html/nedi/Other-Converter.php or within any installed NeDi directory under the htdocs or www folderAffected if The file Other-Converter.php exists in the NeDi web directory
-
Confirm txt GET parameter handlingInspect Other-Converter.php source code to verify it accepts a txt GET parameter. Look for code that reads $_GET['txt'] or similar parameter handling without proper sanitizationAffected if The file processes a txt parameter from the URL without validated input
-
Check if web interface is exposedDetermine if the NeDi web interface is accessible over the network. Test if Other-Converter.php is reachable via HTTP/HTTPS (e.g., curl or browser access to http://[host]/[nedi-path]/Other-Converter.php)Affected if The vulnerable PHP file is accessible via the web server
You are affected if NeDi version 1.9c is installed AND the Other-Converter.php file is present and accessible via the web interface, allowing the txt parameter to be manipulated without input validation.
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 on the txt parameter in Other-Converter.php to prevent XSS execution.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15016 — 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-15016 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