How severe is CVE-2025-63009?

CVE-2025-63009 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2025-63009 being actively exploited?

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

How do I fix CVE-2025-63009?

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

Does CVE-2025-63009 have an EU (EUVD) identifier?

Yes. CVE-2025-63009 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-202000.

When was CVE-2025-63009 published?

CVE-2025-63009 was published on 2025-12-09 and last updated on 2026-06-17.

CVE-2025-63009

CVE-2025-63009 is a medium-severity vulnerability with a CVSS 3.x base score of 5.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-497.

Key facts

Severity: Medium (CVSS 3.x base score 5.3)
EPSS exploit prediction: 0% (16th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-202000
Weakness: CWE-497
Published: 2025-12-09
Last modified: 2026-06-17

Description

Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in yuvalo WP Google Analytics Events wp-google-analytics-events allows Retrieve Embedded Sensitive Data.This issue affects WP Google Analytics Events: from n/a through <= 2.8.2.

Frequently asked questions

What is CVE-2025-63009?: Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in yuvalo WP Google Analytics Events wp-google-analytics-events allows Retrieve Embedded Sensitive Data.This issue affects WP Google Analytics Events: from n/a through <= 2.8.2.
How severe is CVE-2025-63009?: CVE-2025-63009 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2025-63009 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (16th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-63009?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-63009 have an EU (EUVD) identifier?: Yes. CVE-2025-63009 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-202000.
When was CVE-2025-63009 published?: CVE-2025-63009 was published on 2025-12-09 and last updated on 2026-06-17.

References

https://patchstack.com/database/Wordpress/Plugin/wp-google-analytics-events/vulnerability/wordpress-wp-google-analytics-events-plugin-2-8-2-sensitive-data-exposure-vulnerability?_s_id=cve

Other CWE-497 vulnerabilities

CVE-2025-10264 — Critical (CVSS 10.0): Certain models of NVR developed by Digiever has an Exposure of Sensitive Information vulnerability, allowing…
CVE-2026-27494 — Critical (CVSS 9.9): n8n is an open source workflow automation platform. Prior to versions 2.10.1, 2.9.3, and 1.123.22, an authenticated…
CVE-2025-47699 — Critical (CVSS 9.9): Exposure of Sensitive System Information to an Unauthorized Control Sphere (CWE-497) in the Gallagher Morpho…
CVE-2025-44823 — Critical (CVSS 9.9): Nagios Log Server before 2024R1.3.2 allows authenticated users to retrieve cleartext administrative API keys via a…
CVE-2026-14808 — Critical (CVSS 9.8): Prog Management System developed by PROG MIS has a Exposure of Sensitive Information vulnerability, allowing…
CVE-2024-13999 — Critical (CVSS 9.8): Nagios XI versions prior to 2024R1.1.3, under certain circumstances, disclose the server's Active Directory (AD) or…

Browse all CWE-497 vulnerabilities →