dbcve.org
NediApplication

CVE-2020-15034

MEDIUM · 5.4 CVSS v3.1 Published 2020-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
NeDi 1.9C is vulnerable to cross-site scripting (XSS) attack. The application allows an attacker to execute arbitrary JavaScript code via the Monitoring-Setup.php tet 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 confidence

NeDi 1.9C contains a reflected cross-site scripting (XSS) vulnerability in Monitoring-Setup.php via the tet parameter. An attacker can inject arbitrary JavaScript code that executes in the context of the victim's browser when they access the crafted URL.

MitigationSanitize and properly encode the tet parameter input before rendering it in HTML output. Implement context-aware output encoding and consider adding Content-Security-Policy headers to mitigate XSS risks.

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
NediApplication
Affected:= 1.9c

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm NeDi installation and version
    Locate the NeDi installation directory and identify the installed version number (typically found in version files, about pages, or the main NeDi startup/configuration files). Compare it to the affected version 1.9C.
    Affected if The installed NeDi version is exactly 1.9C.
  2. Verify Monitoring-Setup.php exists
    Check if the file Monitoring-Setup.php exists within the NeDi web directory structure (typically in the html or htdocs folder).
    Affected if The file Monitoring-Setup.php exists in the NeDi web root.
  3. Check for unencoded 'tet' parameter reflection
    Access Monitoring-Setup.php with a test 'tet' parameter value (for example: ?tet=test) and inspect the page source or response to see if the value is reflected back into the HTML output without encoding or sanitization.
    Affected if The 'tet' parameter value is reflected in the HTML output without proper encoding (the raw value appears unescaped in the page).

A system is affected if NeDi version 1.9C is installed, the Monitoring-Setup.php file is present, and the 'tet' parameter is being reflected in HTML output without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Sanitize and properly encode the tet parameter input before rendering it in HTML output. Implement context-aware output encoding and consider adding Content-Security-Policy headers to mitigate XSS risks.

Fix this in Nedi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-15034 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-15034 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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