Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running Jane Menu < 1.5.1
-
DeliverySend unauthenticated request to unprotected form handler
-
ExploitBind published page to attacker remote document
-
ExecutionAdmin/visitor loads poisoned page
-
PersistInjected JavaScript runs in their session
-
ImpactHijack admin session / full site compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No authentication is required: the vulnerable form handler performs no capability or nonce check and is reachable by unauthenticated users (PR:N), who can bind any published page to a remote document of their choosing. The sole limiting factor is UI:R - exploitation payload only executes when a user (ideally an administrator) subsequently visits the affected published page; the attacker cannot force this visit directly. The plugin must be installed and at a version before 1.5.1, and the targeted page must be published. No other non-default configuration is required. |
| Impact | This is a genuine high-priority issue, not an inflated high-CVSS score. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R) describes an unauthenticated, network-reachable, low-complexity flaw, and the description confirms it: an unauthenticated form handler with no capability or nonce check lets anyone bind a published page to an attacker-controlled remote document whose unescaped head/body is then rendered - a classic unauthenticated stored XSS. The only gating factor is UI:R (a victim must visit the poisoned page), but because any visitor - explicitly including a logged-in administrator - triggers execution, the realistic outcome is admin-session hijack and full site takeover, which justifies the C:H/I:H/A:H impact. Public exploit code exists (WPScan), raising practical risk, but there is NO CISA KEV listing and NO EPSS score provided, so there is no evidence of active or widespread exploitation - exploitation status is 'exploit available' rather than 'exploited in the wild.' No SSVC decision data was supplied. Net: treat as a real, patch-promptly issue for anyone running the plugin, tempered by the plugin's likely small deployment footprint. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted request to the vulnerable form handler, binding a popular published page to a remote HTML document they host that contains malicious JavaScript. When a site administrator (or any visitor) later loads that page, the injected script executes in their authenticated browser session, enabling cookie/session theft or creation of a rogue admin account. A public proof-of-concept is documented by WPScan. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Unauthenticated stored cross-site scripting in the Jane Menu WordPress plugin before 1.5.1 lets remote attackers bind any published page to an attacker-controlled remote document that the plugin fetches and renders without escaping, causing arbitrary JavaScript to execute for visitors, including administrators. Authentication is not required, but exploitation is not automatic: the payload fires only when a victim visits the tampered published page (UI:R). Publicly available exploit code exists; CISA KEV does not list this CVE, and the independent assessment rates this as a genuine high-priority issue rather than an inflated score.
RemediationAI
Vendor-released patch: 1.5.1. Upgrade Jane Menu to 1.5.1 or later and verify the installed version through the WordPress plugin inventory; the WPScan advisory is at https://wpscan.com/vulnerability/76cfadde-2db5-4e01-b44b-c399381c339b/. If immediate upgrade is not possible, deactivate the plugin because the unauthenticated form handler cannot be safely exposed; the trade-off is loss of menu functionality. Where deactivation is unacceptable, front the site with a WAF or reverse proxy that blocks unauthenticated requests to Jane Menu's page-binding form-handler route, though the exact route must be confirmed from the installed plugin and overly broad blocking may break legitimate menu features. Audit published pages for unexpected remote-document bindings and remove them, and consider a Content Security Policy that restricts script sources as a secondary control, with the trade-off that it can break legitimate inline or third-party scripts.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Jane Menu is a WordPress plugin whose form handler lacks capability and nonce checks, so it is reachable by unauthenticated users. The root cause combines missing authorization/nonce validation with unsafe rendering of a fetched remote document: an attacker can create a page-to-remote-document binding, and the plugin then fetches that document and outputs its head and body into the page without escaping, turning attacker-controlled markup and scripts into stored cross-site scripting. The authoritative assessment uses AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, meaning no privileges are needed, user interaction is required, scope is changed, and confidentiality, integrity, and availability impacts are high. CPE data identifies the affected component as cpe:2.3:a:unknown:jane_menu:*:*:*:*:*:*:*:*, with the vendor string unpopulated, so version confirmation must come from the WordPress plugin inventory (before 1.5.1).
Know when Jane Menu gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Unauthenticated (PR:N), low-complexity remote injection; victim must load the page (UI:R); stored XSS executes in the victim's browser crossing a trust boundary (S:C), and admin-session takeover yields full C/I/A impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
2DescriptionCVE.org
The Jane Menu WordPress plugin before 1.5.1 does not have any capability or nonce checks on one of its form handlers, which is reachable by unauthenticated users, allowing them to bind any published page to a remote document of their choosing. The plugin then fetches that document and outputs its head and body into the page without escaping, so an unauthenticated attacker can run arbitrary JavaScript in the browser of any visitor to that page, including an administrator.
Technical POC Analysis
The bug class is stored cross-site scripting (CWE-79), enabled by a missing authorization check (CWE-862) and missing anti-CSRF token validation (CWE-352) on a state-changing form handler in the Jane…
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Jane Menu, a WordPress plugin used to construct site navigation menus, contains a stored cross-site scripting flaw (CVE-2026-85683, CVSS 8.8) in all versions before 1.5.1 that lets an outside party bind any published page to an attacker-controlled remote document, which the plugin then fetches and renders without escaping so that arbitrary JavaScript runs in the browser of every page visitor, including logged-in administrators. Publicly available exploit code exists and no vendor-released patch is confirmed at time of analysis, so any site running this plugin is exposed to administrator session theft, account takeover, and follow-on compromise of the broader web estate. Leadership should care because a single administrator page view can hand an attacker effective control of a public-facing corporate website, its content, and any customer trust or regulatory obligations attached to it.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate and remove the Jane Menu plugin from all sites until a fixed build is obtained directly from the vendor; where removal is not immediately possible, eliminate any binding of published pages to external or untrusted remote documents and restrict the plugin's ability to fetch remote content at the network or WAF layer; enforce a restrictive Content-Security-Policy that blocks inline and third-party script execution; force session invalidation and credential rotation for all administrator accounts and require administrators to browse public pages from a separate low-privilege browser profile; enable virtual patching at the WAF or reverse proxy to detect and block injected script and unexpected outbound fetch patterns; and monitor web and plugin logs for anomalous remote document requests pending permanent remediation.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-107148
GHSA-2849-7xm6-r42x
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB