CVE-2026-1822
Stored XSS in WP NG Weather Plugin via 'ng-weather' Shortcode
Publication date: 2026-03-21
Last updated on: 2026-03-21
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wp_ng_weather | ng_weather | to 1.0.9 (inc) |
| wordfence | wp_ng_weather | to 1.0.9 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The WP NG Weather plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) via its 'ng-weather' shortcode in all versions up to and including 1.0.9. This vulnerability arises because the plugin does not properly sanitize or escape user-supplied attributes. As a result, authenticated users with contributor-level access or higher can inject arbitrary web scripts into pages. These scripts will execute whenever any user accesses the injected page.
How can this vulnerability impact me? :
This vulnerability allows attackers with contributor-level access or above to inject malicious scripts into pages via the plugin's shortcode attributes. When other users visit these pages, the injected scripts execute in their browsers. This can lead to theft of user credentials, session hijacking, defacement, or other malicious actions performed in the context of the affected website.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability involves stored Cross-Site Scripting (XSS) via the 'ng-weather' shortcode in the WP NG Weather WordPress plugin versions up to 1.0.9. Detection would involve identifying if this plugin and vulnerable versions are installed and if any pages contain injected scripts via this shortcode.
Since the vulnerability requires authenticated users with contributor-level access or higher to inject scripts, detection can include scanning WordPress installations for the presence of the WP NG Weather plugin version 1.0.9 or earlier.
Specific commands to detect the plugin version or presence might include:
- Using WP-CLI to check installed plugins and their versions: `wp plugin list | grep wp-ng-weather`
- Searching for the shortcode usage in WordPress content database: `wp db query "SELECT ID, post_content FROM wp_posts WHERE post_content LIKE '%[ng-weather]%'"`
- Checking for suspicious script injections in pages using the shortcode by reviewing the post_content field for script tags or unusual JavaScript.
Network detection of exploitation attempts is difficult because the attack is stored and executes in the context of a user visiting the infected page. Monitoring HTTP responses for injected scripts in pages containing the shortcode could help.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Update the WP NG Weather plugin to a version later than 1.0.9 where the vulnerability is fixed, if available.
- If an update is not available, temporarily disable or remove the WP NG Weather plugin to prevent exploitation.
- Restrict contributor-level and higher user permissions to trusted users only, as the vulnerability requires authenticated users with such access.
- Review and sanitize existing content using the 'ng-weather' shortcode for injected scripts and remove any malicious code.
- Implement Web Application Firewall (WAF) rules to detect and block attempts to inject scripts via the shortcode attributes.