Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-62118: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in kcseopro AdWords Conversion Tracking Code

0
Medium
VulnerabilityCVE-2025-62118cvecve-2025-62118cwe-79
Published: Wed Dec 31 2025 (12/31/2025, 12:59:08 UTC)
Source: CVE Database V5
Vendor/Project: kcseopro
Product: AdWords Conversion Tracking Code

Description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in kcseopro AdWords Conversion Tracking Code allows Stored XSS.This issue affects AdWords Conversion Tracking Code: from n/a through 1.0.

AI-Powered Analysis

AILast updated: 01/20/2026, 22:27:06 UTC

Technical Analysis

CVE-2025-62118 identifies a Stored Cross-Site Scripting (XSS) vulnerability in the kcseopro AdWords Conversion Tracking Code, a tool used to track advertising conversions on websites. The vulnerability stems from improper neutralization of input during web page generation (CWE-79), which allows attackers to inject malicious JavaScript code that is stored persistently and executed in the context of users visiting the affected web pages. This can lead to unauthorized actions such as session hijacking, cookie theft, defacement, or redirection to malicious sites. The vulnerability affects all versions up to 1.0 of the product, with no patches currently available. The CVSS 3.1 base score is 6.5, indicating a medium severity level, with attack vector being network-based (AV:N), low attack complexity (AC:L), requiring privileges (PR:L), and user interaction (UI:R). The scope is changed (S:C), meaning the vulnerability can affect components beyond the initially vulnerable component. The impact on confidentiality, integrity, and availability is low to medium. No known exploits have been reported in the wild yet. The vulnerability was reserved in October 2025 and published at the end of 2025. The kcseopro AdWords Conversion Tracking Code is likely integrated into websites that rely on Google Ads conversion tracking, making it relevant for organizations involved in digital marketing and e-commerce.

Potential Impact

For European organizations, this vulnerability poses risks primarily to web applications that integrate the kcseopro AdWords Conversion Tracking Code for tracking advertising performance. Exploitation could allow attackers to execute malicious scripts in the browsers of site visitors, potentially leading to theft of sensitive information such as session tokens, personal data, or credentials. This can result in account compromise, unauthorized transactions, or reputational damage. Additionally, attackers could manipulate website content or redirect users to phishing or malware sites, impacting user trust and compliance with data protection regulations like GDPR. The medium severity and requirement for some privileges and user interaction reduce the likelihood of widespread automated exploitation, but targeted attacks against high-value organizations remain a concern. The lack of patches increases exposure until mitigations are implemented. Given the importance of digital advertising and e-commerce in Europe, especially in countries with large online markets, the impact could be significant if exploited.

Mitigation Recommendations

Organizations should immediately audit their web properties to identify usage of the kcseopro AdWords Conversion Tracking Code. Until an official patch is released, implement strict input validation and output encoding on all user-supplied data that interacts with the tracking code to prevent injection of malicious scripts. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS attacks. Monitor web application logs for unusual activity or injection attempts. Limit privileges of accounts that can modify tracking code configurations to reduce attack surface. Educate developers and administrators about secure coding practices related to input handling. Once patches or updates become available from the vendor, prioritize their deployment. Additionally, consider using web application firewalls (WAFs) with rules designed to detect and block XSS payloads targeting this vulnerability. Regularly review and update security policies to ensure compliance with data protection laws.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-10-07T15:41:34.897Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69552191db813ff03ee950e2

Added to database: 12/31/2025, 1:13:53 PM

Last enriched: 1/20/2026, 10:27:06 PM

Last updated: 2/4/2026, 10:45:23 AM

Views: 41

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats