HIGH 7.1

CVE-2025-68872: Unauthenticated XSS in Eli's WordCents adSense Widget (CVSS 7.1)

A security flaw in Eli's WordCents adSense Widget with Analytics (version 1.3.03.27 and earlier) allows attackers to inject malicious scripts into web pages without requiring authentication. When a user visits an affected page, the injected code executes in their browser, potentially stealing session cookies, redirecting them to phishing sites, or capturing form input. The vulnerability stems from insufficient validation of user-supplied input before displaying it on the page.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.1 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Weaknesses (CWE)
CWE-79
Affected products
0 configuration(s)
Published / Modified
2026-06-15 / 2026-06-17

NVD description (verbatim)

Unauthenticated Cross Site Scripting (XSS) in Eli&#039;s WordCents adSense Widget with Analytics <= 1.3.03.27 versions.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2025-68872 is an unauthenticated Cross-Site Scripting (XSS) vulnerability (CWE-79) affecting Eli's WordCents adSense Widget with Analytics through version 1.3.03.27. The plugin fails to properly sanitize or escape user-controlled input before rendering it in the DOM, allowing arbitrary JavaScript execution in the context of affected websites. The attack vector is network-based, requires no privilege escalation, and depends on user interaction (UI:R)—typically a visit to a compromised or attacker-controlled page featuring the vulnerable widget.

Business impact

This vulnerability poses a direct threat to WordPress site owners and their visitors. Compromised sites can be weaponized to harvest credentials, distribute malware, deface content, or redirect users to attacker-controlled domains. For e-commerce or SaaS sites using this widget, the risk extends to customer data breaches and reputational damage. The wide deployment of WordPress plugins amplifies the potential blast radius if exploitation becomes widespread.

Affected systems

Eli's WordCents adSense Widget with Analytics version 1.3.03.27 and all prior releases are vulnerable. The plugin is likely distributed through WordPress.org or third-party theme/plugin marketplaces. Any WordPress installation with this plugin active is at risk. Site owners should verify their installed version immediately and check the plugin repository or vendor website for current version status.

Exploitability

Exploitation requires no authentication, making the barrier to attack extremely low. Attackers can craft malicious links or embed payloads in comments, forum posts, or any user-controlled content that passes through the vulnerable widget. The need for user interaction (visiting a page where the payload is rendered) is a minor friction point in practice, as many attack scenarios—such as compromised ads or injected ads in ad networks—can naturally satisfy this requirement. The attack complexity is low (AC:L), indicating straightforward payload delivery.

Remediation

Update Eli's WordCents adSense Widget with Analytics to a patched version beyond 1.3.03.27. Verify the exact patch version against the official plugin page or vendor advisory before deployment. If no patch is immediately available, consider disabling or removing the plugin entirely until a fix is released. Additionally, review WordPress user roles and plugin capabilities to restrict admin access and limit who can manage plugin settings or modify widget configuration.

Patch guidance

Check the official Eli's WordCents adSense Widget with Analytics plugin page on WordPress.org (or the vendor's site) for version 1.3.03.28 or later. Test patches in a staging environment before rolling out to production. If the vendor has issued a security advisory with specific version numbers, verify the patch version explicitly before applying. After patching, confirm the plugin is functioning correctly and audit any recent logs for signs of exploitation during the window when the site ran the vulnerable version.

Detection guidance

Monitor web server logs and WordPress security logs for unusual GET or POST requests targeting the widget's configuration parameters or those commonly used in XSS payloads (e.g., requests containing script tags, event handlers, or encoded JavaScript). Use WordPress security plugins (e.g., Wordfence, Sucuri) to scan for vulnerable plugin versions and malicious scripts. Review page source and network traffic for unexpected inline scripts or external script inclusions. Consider enabling Content Security Policy (CSP) headers to restrict script execution and provide an additional layer of defense against injected code.

Why prioritize this

With a CVSS 3.1 score of 7.1 (HIGH), this vulnerability merits prompt attention. The combination of unauthenticated access, network reachability, cross-site impact (S:C), and confirmed integrity compromise (ability to modify page content and execute arbitrary code) makes it a serious risk. Although it does not currently appear on the CISA KEV list, the ease of exploitation and potential for large-scale compromise warrant rapid patching, especially for public-facing or customer-facing WordPress sites.

Risk score, explained

The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) reflects a network-accessible vulnerability requiring no privilege or authentication, but dependent on user interaction. The scope change (S:C) indicates the impact extends beyond the vulnerable component—injected scripts affect the entire page and user session. Confidentiality, integrity, and availability are all rated as low to limited impact individually, but in aggregate they represent a HIGH-severity issue due to the ease of exploitation and the breadth of affected users.

Frequently asked questions

Does this vulnerability affect my WordPress site if I don't use Eli's WordCents adSense Widget?

No. This CVE is specific to the Eli's WordCents adSense Widget with Analytics plugin. If you don't have this plugin installed or active, you are not directly affected. However, always keep all plugins updated as a general security hygiene practice.

What should I do if I use this plugin but cannot update immediately?

Disable the plugin until a patch is available. You can do this via the WordPress admin dashboard (Plugins > Installed Plugins, then Deactivate). If the widget is critical to your site's functionality, consider using an alternative ad management solution in the interim. Also review recent traffic logs to check for signs of exploitation.

Can an attacker exploit this without my WordPress admin credentials?

Yes. This is an unauthenticated XSS, meaning no WordPress login is required. An attacker can inject malicious code by crafting a specially formatted URL or embedding a payload in user-generated content (comments, forum posts, etc.) that the vulnerable widget processes and displays.

Will updating my WordPress core or other plugins fix this automatically?

No. You must explicitly update the Eli's WordCents adSense Widget with Analytics plugin itself. WordPress does not automatically patch third-party plugins. Log into your WordPress dashboard, go to Plugins > Installed Plugins, and update this plugin to the latest available version.

This analysis is based on publicly disclosed vulnerability data as of the modification date (2026-06-17). Patch availability and specific remediation guidance should be verified against the official vendor advisory and WordPress.org plugin repository. SEC.co does not provide warranty or legal guarantee regarding the completeness or accuracy of patch information. Organizations should conduct their own risk assessment based on their specific deployment and threat model. No exploit code or proof-of-concept is provided in this document. Source: NVD (public-domain), retrieved 2026-07-23. Analysis generated by SEC.co (claude-haiku-4-5).