Skip to content
Laskyr

Plugins · widget-context · data as of 2026-11-04

Is Widget Context safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (1.5.0)

As of 2026-11-04. 1 issue is on record for older versions; version 1.4.0 or newer fixes all of them that state a fix.

Latest version
1.5.0
Last updated
2026-10-09
Active installs
30,000+
Known issues on record
1
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 7.4+

Show and hide widgets on specific posts, pages and sections of your site. — by Kaspars

What to do

  1. Update to the latest version (1.5.0). Anything older than 1.4.0 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get widget-context --field=version shows what you run; wp plugin update widget-context updates it.

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 4.3 CVE-2026-7615 · published 2026-05-22

Cross-site request forgery (CSRF) in Widget Context (1.3.3 and older)

Affected
1.3.3 and older
Fixed in
1.4.0 *
Access needed (per CVSS)
No login needed; someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The Widget Context plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.3.3. This is due to missing or incorrect nonce validation on the save_widget_context_settings function. This makes it possible for unauthenticated attackers to modify widget visibility context settings stored in the WordPress options table via a forged POST request to /wp-admin/widgets.php via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

NVD CVE-2026-7615Wordfence advisorygithub.comPlugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Widget Context vulnerability status badge
<a href="https://laskyr.com/plugins/widget-context"><img src="https://laskyr.com/plugins/widget-context/badge.svg" alt="Widget Context vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit