ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-7615

The Widget Context plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.3.3.

Published May 22, 2026 · catalog updated Jul 23, 2026 · The Widget Context plugin

Check if you run it

No confirmed exploitation is on record for CVE-2026-7615. EPSS is 0.20%. Act only if a listed version of The Widget Context plugin is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (The Widget Context plugin).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.20%
Remediation
Version ranges on file
Affected products
stated named in the record

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • stated named in the record<= 1.3.3

How to fix CVE-2026-7615

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-7615. EPSS is 0.20%. Act only if a listed version of The Widget Context plugin is installed.

Which versions are affected?

Compare what you have installed with named in the record <= 1.3.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-352: Cross-Site Request Forgery (CSRF). EPSS 0.20%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

WordPress security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. May 22, 2026 · NIST NVD

    Detected

    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-adm

  2. Jul 23, 2026 · NIST NVD

    Updated

    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-adm

Sources

  • CVE.orgVulnerability recordCVE-2026-7615

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-7615

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDVulnerability recordCVE-2026-7615

    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

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.