Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2020-36529SevOne Network Management System Traceroute traceroute.php command injection

Description

A vulnerability classified as critical has been found in SevOne Network Management System up to 5.7.2.22. This affects the file traceroute.php of the Traceroute Handler. The manipulation leads to privilege escalation with a command injection. It is possible to initiate the attack remotely.

Public exploit

An exploit or proof of concept is public: anyone can try it against an unpatched system. CISA's SSVC rates its exploitation: a proof of concept is public.

Timeline

  1. ID reserved

    By VulDB

  2. Published

  3. · 3 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2020-36529, by who scored it
Scored byCVSSScoreVector
VulDBCNA (assigner)3.1High8.8CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High8.8CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
3.8% · top 9.8% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: poc · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • SevOne · Network Management System

    • affected 5.7.2.0
    • affected 5.7.2.1
    • affected 5.7.2.2
    • affected 5.7.2.3
    • affected 5.7.2.4
    • affected 5.7.2.5
    • affected 5.7.2.6
    • affected 5.7.2.7
    • affected 5.7.2.8
    • affected 5.7.2.9
    • affected 5.7.2.10
    • affected 5.7.2.11
    • affected 5.7.2.12
    • affected 5.7.2.13
    • affected 5.7.2.14
    • affected 5.7.2.15
    • affected 5.7.2.16
    • affected 5.7.2.17
    • affected 5.7.2.18
    • affected 5.7.2.19
    • affected 5.7.2.20
    • affected 5.7.2.21
    • affected 5.7.2.22

References

References2

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2020-36529 badge
[![CVE-2020-36529](https://cveledger.app/badge/CVE-2020-36529.svg)](https://cveledger.app/cve/CVE-2020-36529)

Record last updated .