How severe is CVE-2005-1716?

CVE-2005-1716 has a CVSS 2.0 base score of 5.0, rated medium severity.

Is CVE-2005-1716 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (72nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2005-1716?

CVE-2005-1716 primarily affects Ej3 Topo. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-1716?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2005-1716 published?

CVE-2005-1716 was published on 2005-05-24 and last updated on 2026-06-16.

CVE-2005-1716

CVE-2005-1716 is a medium-severity vulnerability in Ej3 Topo with a CVSS 2.0 base score of 5.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 5.0)
EPSS exploit prediction: 2% (72nd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Ej3 Topo
Published: 2005-05-24
Last modified: 2026-06-16

Description

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.

Frequently asked questions

What is CVE-2005-1716?: 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 severe is CVE-2005-1716?: CVE-2005-1716 has a CVSS 2.0 base score of 5.0, rated medium severity.
Is CVE-2005-1716 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (72nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-1716?: CVE-2005-1716 primarily affects Ej3 Topo. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-1716?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2005-1716 published?: CVE-2005-1716 was published on 2005-05-24 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:ej3:topo:2.2:*:*:*:*:*:*:*
cpe:2.3:a:ej3:topo:2.2.178:*:*:*:*:*:*:*

More vulnerabilities in Ej3 Topo

CVE-2006-3536 — High (CVSS 7.5): Direct static code injection vulnerability in code/class_db_text.php in EJ3 TOPo 2.2.178 and earlier allows remote…
CVE-2006-3833 — Medium (CVSS 5.0): index.php in EJ3 TOPo 2.2.178 allows remote attackers to overwrite existing entries and establish new passwords for the…
CVE-2006-3834 — Medium (CVSS 5.0): EJ3 TOPo 2.2.178 includes the password in cleartext in the ID field to index.php, which allows context-dependent…
CVE-2003-1409 — Medium (CVSS 5.0): TOPo 1.43 allows remote attackers to obtain sensitive information by sending an HTTP request with an invalid parameter…
CVE-2006-0984 — Medium (CVSS 4.3): Cross-site scripting (XSS) vulnerability in inc_header.php in EJ3 TOPo 2.2.178 allows remote attackers to inject…
CVE-2005-1715 — Medium (CVSS 4.3): Cross-site scripting (XSS) vulnerability in index.php for TOPo 2.2 (2.2.178) allows remote attackers to inject…

All CVEs affecting Ej3 Topo →