CVE-2020-15029
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 Assets-Management.php sn 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 the Assets-Management.php page via the 'sn' parameter. An attacker can inject arbitrary JavaScript code that executes in the context of a victim's browser when they interact with the crafted payload.
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 file or about page. Typical paths include /var/www/nedi or C:\xampp\htdocs\nedi. Look for version.php, about.php, or check the login page footer for version information.Affected if The installed version is exactly 1.9C (case-sensitive match to '1.9c')
-
Verify Assets-Management.php existsCheck if the file Assets-Management.php exists in the NeDi web root directory. This file is required for the vulnerability to be present.Affected if The file Assets-Management.php exists in the NeDi installation
-
Confirm web interface accessibilityVerify the NeDi web interface is accessible over HTTP/HTTPS. The XSS requires a user to interact with the vulnerable page.Affected if The NeDi web interface is accessible and the Assets-Management.php page can be reached
-
Test the sn parameter for XSS vulnerabilityIf the above conditions are met, manually test by submitting a benign XSS payload like <script>alert(1)</script> to the 'sn' parameter in Assets-Management.php (e.g., Assets-Management.php?sn=<script>alert(1)</script>) and observe if the script executes in the browser.Affected if The 'sn' parameter reflects the injected input without sanitization and the script executes in the browser context
A user is affected if NeDi version 1.9C is installed, the Assets-Management.php page exists and is accessible, and the 'sn' parameter reflects unsanitized input leading to script execution.
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 input validation and output encoding to the 'sn' parameter in Assets-Management.php. Update to a patched version if available from the vendor.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15029 — 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-15029 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