CVE-2026-15385 - Before 1 Plugin
CVE-2026-15385
The RT Mega Menu WordPress plugin before 1.5.2 does not perform a capability check on the AJAX action that saves mega-menu configuration and per-menu-item settings; its only gate is a nonce that any logged-in user can read from a standard admin page. A subscriber-level user can therefore enable the mega menu on a site menu and store a menu-item style value that is rendered, without output escaping, into a style attribute on the public navigation. By breaking out of that attribute the user persists a JavaScript event handler that executes for every visitor who hovers the navigation, including administrators, leading to session/site takeover.
CVE-2026-15385
UNKNOWN
CVSS 0.0
Published 2026-08-02
Updated 2026-08-02
AI Risk Low (5/100)
Active Exploit: No strong signal
Published Exploit: No public exploit references
Priority: P5 Monitor
Severity Band
UNKNOWN
CVSS Vector
Unspecified
Affected Components
2
Reference Links
1
AI Risk Engine
Low (5/100)
Exploitability
Low
Active Exploitation
No strong signal
Published Exploit Status
No public exploit references
AI Context
Machine-generated threat intelligence
AI
Updated 1 day ago
AI enriched 1 day ago (2026-08-02 20:26 UTC)
Technical Summary
The RT Mega Menu WordPress plugin before 1.5.2 does not perform a capability check on the AJAX action that saves mega-menu configuration and per-menu-item settings; its only gate is a nonce that any logged-in user can read from a standard admin page. A subscriber-level user can therefore enable the mega menu on a site menu and store a menu-item style value that is rendered, without output escaping, into a style attribute on the public navigation. By breaking out of that…
Potential Impact
Severity is UNKNOWN (CVSS 0.0). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.
Exploitability Assessment
Exploitability is assessed as Low based on severity and technical exposure profile.
Primary risk drivers: severity and technical exposure profile
Mitigation Recommendations
Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.
Detection & Monitoring
Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.
Business Impact Lens
AI risk score 5/100 (Low, Low) with priority P5 Monitor. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.