---
id: "CVE-2026-85683"
kind: "vulnerability"
aliases: ["CVE-2026-85683"]
title: "Jane Menu WordPress plugin: unauthenticated visitors can inject scripts into pages"
severity: "high"
cvss: 8.8
epss: 0.00276
exploited: false
status: "open"
category: "package"
products: [{"name": "jane-menu", "fixed": ["1.5.1"], "affected": ">= 0, < 1.5.1", "ecosystem": "wordpress"}]
ecosystems: ["wordpress"]
tags: ["jane-menu", "package", "unauthenticated", "wordpress", "wordpress-plugin", "xss"]
not_affected_if: ["jane-menu-version-1.5.1-or-later", "plugin-not-installed", "version-1.5.1-or-later"]
published_at: "2026-10-21T09:17:08+00:00"
first_seen_at: "2026-10-23T21:57:28+00:00"
updated_at: "2026-10-24T13:15:54+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-85683", "first_seen_at": "2026-10-23T21:57:28+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-10-23T23:48:45+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-85683", "first_seen_at": "2026-10-24T13:15:54+00:00"}]
---

# Jane Menu WordPress plugin: unauthenticated visitors can inject scripts into pages

Jane Menu (WordPress plugin, about 200 active installs) before 1.5.1 has a store-config form handler with no capability or nonce check. An unauthenticated visitor can bind any published page to a remote document of their choosing. The plugin fetches that document and prints its head and body unescaped. The result is stored XSS in every visitor's browser, including admins. CVSS 8.8 (user interaction required). Found by Naoki Kawahigashi, coordinated by WPScan.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- wordpress:jane-menu affected >= 0, < 1.5.1 fixed 1.5.1

## How to check

Run 'wp plugin get jane-menu --field=version' or open Plugins in wp-admin. Anything below 1.5.1 is vulnerable. Since 1.3.8 the plugin injects a tag with its version into the page head, so you can also view-source on a store-menu page. Also review the Jane Menu store configs (the Proxy URL per page) for entries you did not create, and check store-menu pages for unexpected script tags.

## Fix

Update Jane Menu to 1.5.1 or later (current release on wordpress.org). If you cannot update, deactivate the plugin. Then remove any unknown store configs and check page content for injected scripts. If an admin visited an affected page, consider rotating sessions.

## Timeline

- 2026-10-23T21:57:28+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-85683
- 2026-10-23T23:48:45+00:00 analyst — WPScan (researcher Naoki Kawahigashi) and CVE record: affected <1.5.1, fixed 1.5.1. The exact handler name is not public: WPScan holds the PoC until 2026-11-19. The title says the injection is via the store config Proxy URL. The 1.5.1 changelog does not mention this fix; the 1.5.0 entry says admin permission checks were strengthened, so I could not confirm which release closed the handler. No public PoC and no exploitation evidence found. X has 1 post, not pulled.
- 2026-10-24T13:15:54+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-85683

## Documents

- [advisory] Jane Menu < 1.5.1 – Unauthenticated Stored XSS via Store Config Proxy URL (WPScan) https://wpscan.com/vulnerability/76cfadde-2db5-4e01-b44b-c399381c339b/
- [advisory] CVE Record CVE-2026-85683 https://www.cve.org/CVERecord?id=CVE-2026-85683
- [fix] Jane Menu plugin page and changelog https://wordpress.org/plugins/jane-menu/

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_