← BACK TO ALL INCIDENTS
HIGH

INCIDENT REPORT #005

WordPress XSS Attacks Target Ninja Forms and WooCommerce Plugins to Install Hidden Backdoors

Security researchers observed an October 2026 campaign exploiting stored cross-site scripting vulnerabilities in Ninja Forms and WPC Product Bundles for WooCommerce. Malicious JavaScript targeted authenticated WordPress administrators to install a deceptive plugin, create hidden administrator accounts and establish persistent backdoor access. Security updates are available, but websites where the payload executed may require investigation beyond plugin updates.

PUBLISHED
SEVERITY
HIGH
INCIDENT CLASS
EXPLOITATION OBSERVED / STORED XSS / ADMINISTRATOR ACCOUNT PERSISTENCE
STATUS
PUBLISHED

01 / OVERVIEW

Overview

Security researchers observed an October 2026 campaign exploiting stored cross-site scripting vulnerabilities in Ninja Forms and WPC Product Bundles for WooCommerce. Malicious JavaScript targeted authenticated WordPress administrators to install a deceptive plugin, create hidden administrator accounts and establish persistent backdoor access. Security updates are available, but websites where the payload executed may require investigation beyond plugin updates.

ENVIRONMENT
WordPress websites using WPC Product Bundles for WooCommerce 8.6.6 or earlier, or Ninja Forms 3.15.3 or earlier, where malicious stored content is subsequently viewed in an authent
INCIDENT CLASS
EXPLOITATION OBSERVED / STORED XSS / ADMINISTRATOR ACCOUNT PERSISTENCE
PROVENANCE
PUBLIC-SOURCE TECHNICAL ANALYSIS

02 / SITUATION

Situation

On 4 October 2026, Patchstack recorded exploitation attempts against a stored cross-site scripting (XSS) vulnerability in WPC Product Bundles for WooCommerce (CVE-2026-93836). On 5 October, the same malicious JavaScript payload appeared in attacks against an unrelated stored XSS flaw in Ninja Forms (CVE-2026-94504).

Both vulnerabilities permitted an unauthenticated attacker to submit malicious content that could later execute as JavaScript when a logged-in WordPress administrator viewed the stored WooCommerce order data or Ninja Forms submission in the affected administrative interface. The administrator's authenticated browser context supplied the permissions needed for the attacker's second-stage activity.

Researchers observed both vectors loading a common JavaScript payload from imgcdn1.com/fz/x.js. This payload attempted to install a malicious WordPress plugin, create a visible administrator and deploy additional backdoors. Patchstack recovered and analysed malicious code that also created a second administrator account hidden from the standard Users screen, introduced a secret login route associated with the site's original owner account and deployed an unauthenticated file-manager component. Some dropped files were backdated and some components lived under mu-plugins, where they may not appear in ordinary plugin listings.

Patchstack published its analysis on 6 October 2026 and stated that the observed exploitation volume was limited in its telemetry. National cyber incident-response bodies subsequently circulated advisories about the activity. The evidence confirms real-world exploitation attempts and a working malicious post-exploitation design; it does not quantify successful compromises or establish continuous campaign activity on 14 November 2026.

Both entry-point vulnerabilities have vendor fixes. WPC Product Bundles for WooCommerce 8.6.7 fixes CVE-2026-93836; Ninja Forms 3.15.4 fixes CVE-2026-94504. Updating blocks the documented vulnerable paths but does not automatically remove malware or attacker-controlled accounts installed earlier.

This report is a public-source technical analysis. It does not describe a SecureMyWP customer investigation, an internal laboratory reproduction or a SecureMyWP recovery outcome.

03 / WHAT WE FOUND

Findings

1. INCIDENT IDENTIFICATION
Affected products: WPC Product Bundles for WooCommerce and Ninja Forms.
WPC Product Bundles: CVE-2026-93836, affected versions through 8.6.6, initial fixed version 8.6.7.
Ninja Forms: CVE-2026-94504, affected versions through 3.15.3, initial fixed version 3.15.4.
Vulnerability class: Unauthenticated stored cross-site scripting (CWE-79), requiring later execution in an authenticated administrator's browser.
Patchstack CVSS assessments: 7.1 (High) for each vulnerability.
Observed campaign: 4–5 October 2026; technical investigation published 6 October 2026.
Classification: EXPLOITATION OBSERVED; no comprehensive count of successful compromises.

2. WPC PRODUCT BUNDLES ENTRY POINT
The attacker placed script-bearing content inside a quantity value associated with WooCommerce bundle items. In affected releases, a numeric prefix could pass quantity validation while retaining additional markup in stored order metadata. When that metadata was displayed to an administrator without suitable escaping, the malicious script could execute. The observed request family involved woosb_ids parameters, particularly a nested qty field.

3. NINJA FORMS ENTRY POINT
The attacker used the public form-submission workflow, including the normal AJAX action nf_ajax_submit. Malicious values stored in textarea submissions could be rendered without adequate encoding by the affected legacy administrative submissions editor. Viewing those submissions in a logged-in administrator session could launch the same second-stage JavaScript.

4. SHARED POST-EXPLOITATION PAYLOAD
Researchers tied the two vectors to a common JavaScript source, imgcdn1.com/fz/x.js, with accompanying infrastructure at imgcdn1.com/fz/c.php. The payload operated in an authenticated administrator's browser and tried to perform privileged WordPress actions, including installing an attacker-provided plugin and creating an administrator account. The domain is a historical indicator, not proof of a current active campaign.

5. MULTIPLE PERSISTENCE ROUTES
The recovered plugin was disguised as a benign component named WP Smart Thumbnails, with a directory indicator wp-smart-thumbnails. Researchers identified a heavily packed unauthenticated file manager, a second administrator hidden from the normal Users interface, a secret login route granting access as the original owner account, and other persistence files in must-use plugin locations. Backdated timestamps were used to make malicious components appear older.

6. EVIDENCE AND INDICATORS
Investigate unexpected plugins named or resembling WP Smart Thumbnails, unexpected files in wp-content/mu-plugins/, administrator account records that exist in the WordPress database but do not appear in the Users UI, unexplained plugin installations or user creation events following an administrator viewing orders/submissions, and requests to imgcdn1.com/fz/x.js or /fz/c.php. Investigate web access logs for malicious stored-form submissions, nested woosb_ids quantity fields containing HTML/JavaScript, unusual nf_ajax_submit submissions and later admin-side activity.
Patchstack observed request source IPs 204.8.96.109, 147.90.235.22, 90.184.10.74, 94.16.115.121 and 43.250.53.42. These are historical investigation pivots, not sufficient evidence by themselves.
Absence of these indicators is not proof of a clean site; filenames, infrastructure and loader variants can change.

7. RELEVANT SECURITY BOUNDARIES
An unauthenticated attacker could plant the stored data, but successful browser-side post-exploitation required an authenticated administrator to view the affected content. The malware abused that administrator's permissions. This is distinct from unauthenticated server-side PHP remote code execution through the XSS vulnerability itself.

8. PATCH STATUS AND LIMITATIONS
Minimum fixes: WPC Product Bundles 8.6.7 and Ninja Forms 3.15.4. Use the latest trusted, compatible vendor-supported releases rather than stopping at the minimum fixed versions, as subsequent releases may address other issues.
A patched plugin prevents this documented entry point but cannot establish that previous attacker-created users, must-use plugins or backdoor files have been removed.

9. EXPLOITATION CONFIDENCE
Vulnerabilities and fixed versions: Confirmed.
Observed delivery attempts across both plugins: Confirmed in Patchstack telemetry.
Analysed malicious payload and persistence components: Confirmed.
Total number of successfully compromised sites: Not established.
Continuing activity as of 14 November 2026: Not established.
Overall technical evidence confidence: HIGH.

04 / WHAT WE DID

Actions taken

DOCUMENTED EXTERNAL ACTIONS
Patchstack investigated malicious traffic, linked two stored XSS delivery vectors to a common JavaScript payload, recovered and analysed the secondary malware plugin and published indicators on 6 October 2026. The affected plugin vendors issued security fixes: WPC Product Bundles 8.6.7 and Ninja Forms 3.15.4. National cyber authorities and independent security reporters published defensive advisories.

SECUREMYWP SCOPE NOTE
SecureMyWP did not remediate an identified customer site for this report. The following steps are recommended investigation and response actions, not completed SecureMyWP work.

RECOMMENDED WEBSITE RESPONSE
1. Inventory sites using WPC Product Bundles for WooCommerce or Ninja Forms. Verify installed version, relevant historical update periods, and whether vulnerable content was accessible to site administrators.
2. Preserve suspicious form submissions, WooCommerce order records, web server logs, WordPress audit logs, relevant database entries and suspicious files where practical before deleting content.
3. Update WPC Product Bundles to at least 8.6.7 and Ninja Forms to at least 3.15.4, preferably the newest supported releases from trusted vendors. Confirm the updates completed.
4. Review WooCommerce order metadata and Ninja Forms stored submissions for unexpected script elements or references to attacker-controlled external JavaScript, without executing the content in a privileged browser.
5. Search for suspicious plugin installation events, especially shortly after an administrator accessed affected orders or form submissions.
6. Inspect installed plugins, must-use plugin directories and file-system locations for the WP Smart Thumbnails disguise, unexpected files, heavily obfuscated PHP and files with suspiciously backdated timestamps. Preserve forensic copies before removal.
7. Independently enumerate database user records and their effective capabilities. Do not rely only on the standard WordPress Users interface, because the malware was designed to conceal an administrator there.
8. Investigate unfamiliar login routes and evidence of sessions authenticating as the oldest/original administrator account. Review hosting logs for attempts to access malicious file-manager endpoints.
9. If the post-exploitation implant is confirmed, treat the installation as compromised. Revoke administrator sessions, rotate privileged account credentials, hosting and database secrets and other exposed keys as appropriate, and regenerate WordPress authentication salts.
10. Remove confirmed malicious accounts, plugins, must-use components and persistence files. Restore trustworthy WordPress components or a verified clean backup where appropriate, then investigate how the original injection occurred.
11. Run independent integrity checks and review logs and database access after remediation. Verify the hidden user and backdoor paths no longer exist.
12. Escalate to the hosting provider or a qualified incident responder if server-level access, cross-site compromise or unresolved persistence is suspected.
Updating vulnerable plugins alone is not sufficient incident recovery after a successful compromise.

05 / OUTCOME

Outcome

Patchstack documented an October 2026 campaign using two distinct stored XSS vulnerabilities to deliver the same second-stage WordPress malware. The attack design used an authenticated administrator's browser session to install plugins and establish multiple persistent access routes, including a hidden administrator and secret login mechanism.

Security fixes became available in WPC Product Bundles for WooCommerce 8.6.7 and Ninja Forms 3.15.4. The vendor fixes address the documented stored XSS entry points. They do not remove backdoors that may have been planted before patching.

Patchstack characterised observed exploitation volume as limited at the time of publication. The reviewed public evidence does not establish how many websites completed the full infection chain or show that the same campaign remained active as of 14 November 2026.

RESEARCH SOURCES
1. Patchstack, 6 October 2026, Four Ways Back In: The WordPress XSS Campaign That Hides Its Own Admin Account:
https://www.patchstack.com/articles/four-ways-back-in-the-wordpress-xss-campaign-that-hides-its-own-admin-account/
2. Qatar National Cyber Security Agency, 7 October 2026, Actively Exploited WordPress Plugin Vulnerabilities:
https://ncsa.gov.qa/en/media/cybersecurity-advisories/541115
3. Uganda National CERT, 7 October 2026, Ninja Forms and WPC Product Bundles Flaws Being Used to Plant Backdoors:
https://cert.ug/ninja-forms-and-wpc-product-bundles-flaws-being-used-plant-backdoors-wordpress-sites-cve-2026-94504
4. ThaiCERT, 8 October 2026, XSS Vulnerabilities in Ninja Forms and WPC Product Bundles:
https://www.thaicert.or.th/en/2026/10/08/xss-vulnerabilities-in-ninja-forms-and-wpc-product-bundles-exploited-to-attack-wordpress-websites/

VERIFIED OUTCOME RECORDED See report text above for the governed outcome statement.

06 / HARDENING

Hardening and prevention

Maintain current versions of WordPress core, plugins and themes, with particular attention to public-facing form and WooCommerce integrations.
Treat stored customer submissions and order metadata as untrusted input; use appropriate validation and context-sensitive output escaping in custom themes, plugins and administrator interfaces.

Minimise administrator privileges and use role-appropriate accounts for day-to-day form/order review when possible.
Enable multifactor authentication, session auditing and monitoring of privileged WordPress actions.

Use suitable firewall protection and malware monitoring as supporting controls, not substitutes for prompt patching.
Keep detailed audit trails for plugin installation, user creation, privilege changes and must-use plugin modifications.

Compare WordPress database accounts and their capabilities with the administrator interface; hidden users may evade a visual-only review.
Monitor wp-content/mu-plugins/ and other executable locations for new or modified files, including misleadingly backdated timestamps.
Protect configuration credentials, API keys and backups independently of the running WordPress installation.

Avoid viewing suspicious stored HTML in a privileged browser during investigation; use safe inspection and evidence-preservation techniques.
Maintain a tested recovery plan for backdoors, hidden accounts and compromised privileged sessions.

07 / REPORT GOVERNANCE

Report governance

This public report is shown only because it satisfies SecureMyWP's governed publication requirements.

PROVENANCE
PUBLIC-SOURCE TECHNICAL ANALYSIS
PUBLISHED
15 NOV 2026
PUBLIC STATUS
PUBLISHED

24/7 EMERGENCY REQUEST INTAKE

Need urgent help? Submit an emergency request 24/7.

Tell us what's happening and we'll review the incident as quickly as operational capacity allows.

GET HELP NOW

SECUREMYWP // SECURITY ASSURANCE

WORDPRESSSPECIALISTS
SECUREACCESS
24/7 EMERGENCYINTAKE
30-DAY RE-CLEANWARRANTY

PROFESSIONAL WORDPRESS INCIDENT RESPONSE & REMEDIATION