CVE-2019-25465

CVE-2019-25465 is a high-severity vulnerability with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-260.

Key facts

Description

Hisilicon HiIpcam V100R003 contains a directory traversal vulnerability that allows unauthenticated attackers to access sensitive configuration files by exploiting directory listing in the cgi-bin directory. Attackers can request the getadslattr.cgi endpoint to retrieve ADSL credentials and network configuration parameters including usernames, passwords, and DNS settings.

Frequently asked questions

What is CVE-2019-25465?
Hisilicon HiIpcam V100R003 contains a directory traversal vulnerability that allows unauthenticated attackers to access sensitive configuration files by exploiting directory listing in the cgi-bin directory. Attackers can request the getadslattr.cgi endpoint to retrieve ADSL credentials and network configuration parameters including usernames, passwords, and DNS settings.
How severe is CVE-2019-25465?
CVE-2019-25465 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2019-25465 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (39th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2019-25465?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2019-25465 have an EU (EUVD) identifier?
Yes. CVE-2019-25465 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2019-19736.
When was CVE-2019-25465 published?
CVE-2019-25465 was published on 2026-03-11 and last updated on 2026-06-17.

References

Other CWE-260 vulnerabilities

Browse all CWE-260 vulnerabilities →