CVE-2005-1716: TOPo 2.2 (2.2.178) stores data files in the data directory under the web document root with insufficient acces

This month

MEDIUM 5.0DOWNGRADE

CVE-2005-1716 is a medium-severity flaw (CVSS 5.0) affecting topo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

TOPo 2.2 (2.2.178) stores data files in the data directory under the web document root with insufficient access control, which allows remote attackers to obtain sensitive information such as client IP addresses.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	1.5% (top 25%)
CISA exploited list	No
Published	2005-05-24
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: ej3

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2005-05-24 04:00 UTCPublished CVE record published
2026-06-16 22:13 UTCUpdated Record last modified

ej3 topo DOWNGRADE

Affected: 2.2 · 2.2.178

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.2

1. Check installed version

apt-cache policy topo || rpm -q topo || topo --version

2. No fixed release: DOWNGRADE to a release before 2.2 (Debian / Ubuntu)

apt-cache madison topo sudo apt install topo=<VERSION_BEFORE_2.2> sudo apt-mark hold topo

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list topo sudo dnf downgrade topo-<VERSION_BEFORE_2.2> sudo dnf versionlock add topo

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2005-1716?

topo: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-1716 being exploited?

CVE-2005-1716 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2005-1716 affect?

CVE-2005-1716 affects topo. Severity is medium (CVSS 5.0). TOPo 2.2 (2.2.178) stores data files in the data directory under the web document root with insufficient access control, which allows remote attackers to obtain sensitive information such as client IP addresses.

How urgent is CVE-2005-1716?

Priority 41/100. Public exploit reference

Related CVEs

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

References

← Back to latest CVEs