Key facts
| Fact | Detail |
|---|---|
| Product | Ninja Forms (WordPress plugin) |
| Affected versions | 3.15.3 and all older versions |
| Fixed in | 3.15.4 and later; latest release is 3.15.6 |
| Severity | 7.2 High (CVSS 3.1, Wordfence) |
| Who can attack | Anyone on the internet, no login; an administrator must open the entry |
| Exploited | Yes: Patchstack saw attacks on 5 October 2026; not in CISA's KEV catalog as of 23 October 2026 |
| CVE published | 22 September 2026 |
What an attacker can do
Ninja Forms is a WordPress contact form plugin. CVE-2026-94504 is a stored cross-site scripting flaw (XSS: a script saved on your site that runs later in someone else's browser).
A visitor with no account sends a form entry with a script in a multi-line text box. Version 3.15.3 stores it and shows it without the encoding step that stops text running as code. When an administrator opens that entry in the WordPress admin area, the script can do anything they can do.
Patchstack analysed the code used in real attacks on this flaw. When it runs in an administrator's browser, it installs a fake "WP Smart Thumbnails" plugin and creates two administrators, one hidden from the Users screen. It also adds a secret login URL for the oldest administrator and a file manager with no login. These hidden ways back in stay after you remove Ninja Forms, so the attacker keeps the site and your customers' form entries.
Who is affected
Ninja Forms has more than 500,000 active installs. Every version up to and including 3.15.3 is affected, and version 3.15.4 fixes this flaw.
Your site is exposed if it publishes a form with a plain multi-line text box, one without the rich text editor. The attacker needs no login and sends the entry over the internet. The script runs only when an administrator opens that entry in the older Ninja Forms screen that shows one submitted entry.
Later releases fixed more XSS flaws in the same plugin: CVE-2026-90438 affects 3.15.4 and older, CVE-2026-102385 is fixed in 3.15.5 and CVE-2026-110899 is fixed in 3.15.6. Any version before 3.15.6 still has at least one of them.
How to check your version
If you have WP-CLI (the WordPress command-line tool), run this on the server:
wp plugin get ninja-forms --field=version
It prints the version number and nothing else.
Without a command line on the server, log in to the WordPress admin area and open Plugins > Installed Plugins. Read the version shown on the Ninja Forms row.
Version 3.15.3 or lower is vulnerable to this flaw.
What to do now
Update Ninja Forms to 3.15.6 today. There is no vendor workaround.
Updating does not undo an earlier attack, so check for the signs Patchstack lists:
imgcdn1.com,/fz/x.jsor/fz/c.phpin logs that record request bodies (firewall or security plugin logs); plain access logs do not show themimgcdn1.comor</textarea>in stored form entries: search the database with the command below instead of opening entries one by one/wp-content/plugins/wp-smart-thumbnails/, orwp-login.phprequests with_wploginclass-wp-token-validate.phporclass-wp-query-plus 8 characters from 0 to 9 and a to f, in/wp-content/mu-plugins/fz_emer_done_v1orfz_emer_login_tokensin thewp_optionssettings table
The files carry fake old dates, so a search by date misses them. List administrators straight from the database (wp_users joined to wp_usermeta) and compare with the Users screen. Look for @wordpress.org email addresses or names like support, updater, maintenance or backup.
To search stored form entries without opening them, run this on the server:
wp db search imgcdn1.com
If any sign shows up, remove the extra accounts and the fake plugin. Delete the class-wp-token-validate.php and class-wp-query- files and both fz_emer options. The fake plugin includes a file manager that can write any file on the site. Check the rest of wp-content and the database for other changes, or restore a clean backup from before the attack. Then change the WordPress auth salts (secret keys that sign login cookies) and every admin password, oldest administrator first.
Is it being exploited?
Yes. Patchstack reports attacks that use this flaw. It first saw the attack code on 4 October 2026, sent through CVE-2026-93836 in another plugin, WPC Product Bundles for WooCommerce. The next day it saw the same code sent through this Ninja Forms flaw, using the normal form submission URL (/wp-admin/admin-ajax.php with action=nf_ajax_submit). Patchstack published its analysis on 6 October 2026.
On 23 October 2026 this flaw was not in CISA's KEV catalog (the US government list of flaws known to be exploited). The agency's note on the CVE record says "Exploitation: none", but it dates from 22 September 2026, before these attacks.
Wordfence, which issued the CVE ID, scores this flaw 7.2 High on CVSS 3.1 (a 0 to 10 severity scale). That score rates the impact on data as Low, but the attack code Patchstack found is built to give the attacker full admin control.
Get help
Updating closes this flaw. Flaws in your own code get no CVE and no update, and a test of your app is how they are found.
A penetration test of your web app and its API: who can see whose data, and what an attacker can change.
From AED 20,000, excl. 5% VAT
Sources
- CVE-2026-94504 record CVE Program
- CVE-2026-94504 detail NIST National Vulnerability Database
- Ninja Forms: The Contact Form Builder That Grows With You <= 3.15.3 - Unauthenticated Stored Cross-Site Scripting Wordfence Intelligence
- Four ways back in: the WordPress XSS campaign that hides its own admin account Patchstack
- Ninja Forms changelog (plugin page, Development tab) WordPress.org / Ninja Forms
- Known Exploited Vulnerabilities Catalog CISA
The same update also fixes CVE-2026-92438, CVE-2026-91827, CVE-2026-95515.