Atomic Edge analysis of CVE-2026-1191 (metadata-based): This vulnerability is an authenticated stored cross-site scripting (XSS) flaw in the JavaScript Notifier WordPress plugin. The vulnerability affects the plugin’s settings, allowing attackers with administrator privileges to inject malicious scripts. These scripts execute in the context of any user viewing a page where the plugin’s output is rendered, typically in the site footer via the `wp_footer` action.
The root cause is insufficient input sanitization and output escaping on user-supplied attributes. The CWE-79 classification indicates the plugin fails to properly neutralize user input before it is placed into web page output. Atomic Edge research infers the plugin likely accepts settings via an admin form, stores them without adequate sanitization, and later outputs them directly in the `wp_footer` hook without using escaping functions like `esc_attr()` or `esc_html()`. This conclusion is based on the vulnerability description and common WordPress plugin patterns, as no source code diff is available for confirmation.
Exploitation requires an attacker to have administrator-level access. The attacker would navigate to the plugin’s settings page in the WordPress admin area, typically found at `/wp-admin/options-general.php?page=javascript-notifier` or a similar menu. The attacker would then submit a crafted payload in one of the plugin’s setting fields. A realistic payload could be `` or a script tag loading external JavaScript. Upon saving, the malicious input is stored in the WordPress database. The payload then executes for all users when the plugin renders its output via `wp_footer`.
Remediation requires proper input validation and output escaping. The patched version (1.2.9) likely implemented WordPress sanitization functions like `sanitize_text_field()` on input during settings save operations. For output, the fix would use escaping functions such as `esc_attr()` for HTML attributes and `esc_html()` for text content within the `wp_footer` callback. These functions ensure user-controlled data is treated as inert text, not executable code.
The impact of successful exploitation is client-side code execution in the context of any site visitor. An attacker can steal session cookies, perform actions on behalf of authenticated users, deface the site, or redirect users to malicious domains. The CVSS score of 4.4 reflects the high privileges required (PR:H) and high attack complexity (AC:H), but the scope change (S:C) and low confidentiality/integrity impacts (C:L/I:L) limit the overall severity. The stored nature of the XSS increases its reach compared to reflected attacks.







