Ninja Tables Pro Supply Chain Backdoor (CVE-2026-73533)

Technical Analysis

The vulnerability stems from a compromised software supply chain: the legitimate Ninja Tables Pro update mechanism was replaced with a rogue endpoint that served a tampered 5.2.11 build. The malicious payload, embedded in app/Library/updater/NinjaTableDataSync.php, registers an unauthenticated REST API route acting as a remote backdoor, allowing arbitrary command execution and file writes. Persistence is achieved via must-use plugins (mu-plugins, which load before normal plugins and bypass the standard admin UI), rogue files in wp-content/uploads, a covertly created passwordless WordPress administrator account, and WP-Cron scheduled tasks that reinstate the backdoor even after the malicious plugin is deleted. The CVSS 9.8 score reflects unauthenticated, network-exploitable full compromise with high impact to confidentiality, integrity, and availability. If this WordPress host also runs or exposes AI agent tooling, RAG ingestion pipelines, or stores API keys/secrets used by LLM agents (e.g., in wp-config.php, environment files, or plugin settings), the backdoor could be leveraged to exfiltrate those credentials or pivot into agent infrastructure, making this agent-relevant.

Affected Systems

WordPress installations with Ninja Tables Pro plugin version 5.2.11 downloaded or updated via the decommissioned/rogue update server between the compromise window; any site using automatic plugin updates pointed at the tampered endpoint; shared hosting environments where the compromised site coexists with other applications or secrets.

Indicators of Compromise

• app/Library/updater/NinjaTableDataSync.php
• Rogue REST API endpoint registered under wp-json namespace (backdoor route)
• Unauthorized administrator account (passwordless) in wp_users table
• Unexpected PHP files in wp-content/mu-plugins/
• Unexpected PHP files in wp-content/uploads/
• Unrecognized WP-Cron scheduled events persisting after plugin deletion
• Outbound connections to decommissioned/rogue Ninja Tables update server domain

Remediation Steps

1. 1

   Immediately isolate and audit affected sites

   Take the affected WordPress instance offline or into maintenance mode and perform a full file-integrity scan against a known-clean baseline of the plugin and core WordPress files.

2. 2

   Remove malicious plugin and rogue files

   Delete Ninja Tables Pro 5.2.11 entirely, then manually inspect and clean wp-content/mu-plugins/ and wp-content/uploads/ for injected PHP files, since standard plugin uninstall does not remove these.

3. 3

   Revoke rogue admin accounts and rotate credentials

   Identify and delete any unauthorized administrator accounts, force password resets for all legitimate admins, and rotate WordPress secret keys/salts.

4. 4

   Audit and clear scheduled tasks

   Review wp_options cron entries and server-level cron jobs for persistence mechanisms tied to the backdoor and remove any unrecognized scheduled tasks.

5. 5

   Rotate all exposed secrets and API keys

   Assume any credentials, API keys (including those used by AI agents/LLM integrations), or database secrets stored on the compromised host are exfiltrated; rotate them immediately.

6. 6

   Verify update source integrity

   Confirm the plugin update server in use is the legitimate vendor endpoint, apply the vendor's clean reissued build, and enable signature or checksum verification for future updates.

7. 7

   Deploy monitoring for reinfection

   Add file integrity monitoring and WAF rules to detect recreation of mu-plugins backdoors or rogue REST routes post-cleanup.