CVE-2026-1822
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WP NG Weather plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'ng-weather' shortcode in all versions up to, and including, 1.0.9 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WP NG Weather WordPress plugin up to version 1.0.9 contains a stored XSS vulnerability in its 'ng-weather' shortcode. Authenticated attackers with contributor-level access can inject arbitrary JavaScript through unsanitized shortcode attributes. The plugin fails to sanitize input and escape output, allowing malicious scripts to persist and execute when other users view infected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WP NG Weather plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP NG Weather' or 'ng-weather' in the plugin listAffected if The plugin appears in the installed plugins list
-
Check installed plugin versionClick on the plugin to view its details, or check the plugin header in wp-content/plugins/ng-weather/ng-weather.php for the 'Version' fieldAffected if Version is 1.0.9 or lower
-
Identify pages using the ng-weather shortcodeSearch the WordPress database: SELECT * FROM wp_posts WHERE post_content LIKE '%[ng-weather%' OR use a plugin like Search Regex to scan post_content and postmeta for occurrences of [ng-weatherAffected if Any posts or pages contain the [ng-weather] shortcode
-
Inspect shortcode attributes for unsanitized contentExamine the shortcode usage in post content, for example [ng-weather city="<script>alert(1)</script>"] or any attribute containing quotes, angle brackets, or javascript: patternsAffected if Any shortcode attribute contains raw HTML, script tags, or suspicious JavaScript patterns like <script, javascript:, onload, onerror
You are affected if the WP NG Weather plugin version is 1.0.9 or lower AND any page/post contains the [ng-weather] shortcode with unsanitized attributes in the content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the plugin to the latest version once available, or remove/disable the plugin if no patch exists. Audit all pages using the shortcode for injected malicious content and clean any identified payloads.
Latest version available on wordpress.org (newer than 1.0.9)
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the WP NG Weather plugin
- Check the current version is 1.0.9 or below
- Update the plugin to the latest available version from the WordPress plugin repository
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1822 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1822 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data