PatchTheCVEtopo vulnerabilities and fixes
Recent CVEs affecting topo, with upgrade or downgrade steps. 7 tracked.
topo has 7 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2006-07-25. Highest priority: CVE-2006-3536 (score 45/100).
- CVE-2006-3834 MEDIUM 5.0 DOWNGRADE EJ3 TOPo 2.2.178 includes the password in cleartext in the ID field to index.php, which allows context-depende
- CVE-2006-3833 MEDIUM 5.0 DOWNGRADE index.php in EJ3 TOPo 2.2.178 allows remote attackers to overwrite existing entries and establish new password
- CVE-2006-3536 HIGH 7.5 DOWNGRADE Direct static code injection vulnerability in code/class_db_text.php in EJ3 TOPo 2.2.178 and earlier allows re
- CVE-2006-0984 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in inc_header.php in EJ3 TOPo 2.2.178 allows remote attackers to inje
- CVE-2005-1716 MEDIUM 5.0 DOWNGRADE TOPo 2.2 (2.2.178) stores data files in the data directory under the web document root with insufficient acces
- CVE-2005-1715 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in index.php for TOPo 2.2 (2.2.178) allows remote attackers to inject
- CVE-2003-1409 MEDIUM 5.0 DOWNGRADE TOPo 1.43 allows remote attackers to obtain sensitive information by sending an HTTP request with an invalid p
FAQ
How do I fix topo vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is topo being exploited right now?
None of the tracked topo CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which topo CVE should I patch first?
CVE-2006-3536 currently ranks highest (45/100): Direct static code injection vulnerability in code/class_db_text.php in EJ3 TOPo 2.2.178 and earlier allows re.