Finding and attribution
Ninja Forms plugin for WordPress versions 3.10.4 through 3.14.9 contains an unauthenticated stored cross-site scripting vulnerability in the Repeatable Fieldset feature where parseSubmissionIndex() accepts arbitrary strings as submission indexes without numeric validation, and admin_form_element() interpolates the index directly into HTML without escaping. An unauthenticated attacker can submit a public form with a crafted repeater child key containing malicious script payloads, which execute in an administrator's browser when viewing submissions in the WordPress admin panel, enabling session-cookie theft, creation of administrator accounts, installation of malicious plugins, and…
Product: Ninja Forms. AI system: AISLE AI-native discovery engine (specific model not identified). Team / organization: AISLE.
CVE identifiers: CVE-2026-65048.
AI and human contribution (source account): AISLE’s public CVE index labels this case among findings discovered by its AI-native engine. This is the company’s case-list attribution; the specific model, degree of automation and division of work between AI and people are not identified in the cited sources. The CNA credits: Pavel Kohout, Aisle Research
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The primary CNA record was published 2026-07-21. The reviewed sources do not establish whether the issue was known to defenders before disclosure or exploited in the wild; this classification does not make a zero-day or non-exploitation claim.
Remediation status: not established. The checked vendor changelog lists a correction in 3.14.9, but the case review documents a conflict over whether 3.14.9 is affected for this CVE. The fixed boundary is therefore not stated as settled; no deployment claim is made.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 21 Jul 2026. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Critical · highest recorded score 9.3. Documented technical effects: code execution, data disclosure, privilege escalation, data modification.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-65048: CVSS 4.0 · 9.3 (Critical) ·
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N. CVE Program CNA record · checked 17 Nov 2026. - CVE-2026-65048: CVSS 3.1 · 9.3 (Critical) ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N. CVE Program CNA record · checked 17 Nov 2026.
CVE-2026-65048: code execution, data disclosure, privilege escalation, data modification.
Prerequisites / affected scope: An unauthenticated attacker can submit a public form with a crafted repeater child key containing malicious script payloads, which execute in an administrator's browser when viewing submissions in the WordPress admin panel, enabling session-cookie theft, creation of administrator accounts, installation of malicious plugins, and arbitrary modification of site content..
Exploitation evidence: Exploitation status is not stated in the reviewed CNA/advisory evidence.. Impact source · checked 17 Nov 2026.
Documented fix: The checked vendor changelog lists a correction in 3.14.9, but the case review documents a conflict over whether 3.14.9 is affected for this CVE. The fixed boundary is therefore not stated as settled; no deployment claim is made.