CVE-2025-25522

CVE-2025-25522 is a high-severity vulnerability in Linksys Wap610n Firmware with a CVSS 3.x base score of 7.3. 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-120.

Key facts

Description

Buffer overflow vulnerability in Linksys WAP610N v1.0.05.002 due to the lack of length verification, which is related to the time setting operation. The attacker can directly control the remote target device by successfully exploiting this vulnerability.

Frequently asked questions

What is CVE-2025-25522?
Buffer overflow vulnerability in Linksys WAP610N v1.0.05.002 due to the lack of length verification, which is related to the time setting operation. The attacker can directly control the remote target device by successfully exploiting this vulnerability.
How severe is CVE-2025-25522?
CVE-2025-25522 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity high, and availability low.
Is CVE-2025-25522 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-25522?
CVE-2025-25522 affects Linksys Wap610n Firmware. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-25522?
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-2025-25522 have an EU (EUVD) identifier?
Yes. CVE-2025-25522 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-4120.
When was CVE-2025-25522 published?
CVE-2025-25522 was published on 2025-02-11 and last updated on 2026-06-17.

References

Affected products (1)

Other CWE-120 (Classic Buffer Overflow) vulnerabilities

Browse all CWE-120 (Classic Buffer Overflow) vulnerabilities →