Skip to main content
VulnerabilityPublished

CVE-2026-101326: Ninja Forms (WordPress plugin) · Code Injection

Affects Ninja Forms (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium.

Data as of 31 Oct 2026, 06:06 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.15.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
kstoverNinja Forms – Contact Form Builder with Calculators, Quizzes, Signatures & AI Form BuilderAffected
  • <=3.15.5
Fixed in–

AI-suggested

Since the vulnerability affects all versions up to and including 3.15.5, users should upgrade to a fixed version once available. Until then, administrators should avoid configuring Ninja Forms fields with the {wp:user_display_name} merge tag as a default value on publicly accessible pages to mitigate exploitation. Monitoring vendor advisories for an official fix is recommended.

Description

Ninja Forms – Contact Form Builder with Calculators, Quizzes, Signatures & AI Form Builder plugin for WordPress versions up to 3.15.5 contains a code injection vulnerability. Authenticated users with subscriber-level access or higher can exploit this flaw by setting their display name to a shortcode string and triggering its execution on a page configured by an administrator with a specific merge tag. This allows arbitrary shortcode execution due to improper validation before calling do_shortcode.

References

Community reviews

Loading reviews…