Skip to main content

Conditional Menus CVE-2026-1032

| EUVDEUVD-2026-16171 MEDIUM
Cross-Site Request Forgery (CSRF) (CWE-352)
2026-03-26 Wordfence GHSA-qhrq-phcx-qjv3
4.3
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
4.3 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Lifecycle Timeline

3
EUVD ID Assigned
Mar 26, 2026 - 13:45 euvd
EUVD-2026-16171
Analysis Generated
Mar 26, 2026 - 13:45 vuln.today
CVE Published
Mar 26, 2026 - 13:26 nvd
MEDIUM 4.3

DescriptionCVE.org

The Conditional Menus plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.6. This is due to missing nonce validation on the 'save_options' function. This makes it possible for unauthenticated attackers to modify conditional menu assignments via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

AnalysisAI

Unauthenticated attackers can modify conditional menu assignments in the Conditional Menus WordPress plugin (versions up to 1.2.6) through cross-site request forgery attacks by exploiting missing nonce validation in the save_options function. An attacker can trick site administrators into clicking a malicious link to alter menu configurations without their knowledge. No patch is currently available for this vulnerability.

Technical ContextAI

The Conditional Menus WordPress plugin (CPE: cpe:2.3:a:themifyme:conditional_menus:*:*:*:*:*:*:*:*) is vulnerable due to the absence of nonce validation in its save_options function, which handles menu configuration updates. This is a classic instantiation of CWE-352 (Cross-Site Request Forgery), where a state-changing operation lacks the cryptographic token-based CSRF protections that WordPress provides through its nonce mechanism. The vulnerability exists in the init.php file at lines 183-190, as confirmed by the WordPress plugin repository code browser and changeset 3463814. WordPress nonces are intended to prevent this exact attack class by requiring a time-limited, user-specific token that cannot be forged by an attacker controlling only a victim's browser context.

RemediationAI

Upgrade Conditional Menus to a version newer than 1.2.6, which should include nonce validation in the save_options function as evidenced by the upstream fix in changeset 3463814 at https://plugins.trac.wordpress.org/changeset/3463814/. If an immediate update is not available, restrict WordPress admin access to trusted IP addresses using a Web Application Firewall (WAF) or network-level rules, and educate administrators to avoid clicking links from untrusted sources while logged into WordPress. Implement Content Security Policy (CSP) headers to mitigate some CSRF attack vectors, though this is not a complete substitute for nonce validation. Monitor the official WordPress plugin repository and Wordfence for patch availability notices.

Share

CVE-2026-1032 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy