Skip to main content
Vulnerability Database/CVE-2026-96743

CVE-2026-96743: WordPress Table Field Add-on XSS Vulnerability

CVE-2026-96743 is a stored cross-site scripting flaw in the Table Field Add-on for ACF and SCF WordPress plugin that allows authenticated attackers to inject malicious scripts. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-96743 Overview

CVE-2026-96743 is a Stored Cross-Site Scripting (XSS) vulnerability in the Table Field Add-on for Advanced Custom Fields (ACF) and Secure Custom Fields (SCF) plugin for WordPress. The flaw affects all plugin versions up to and including 1.4.1-RC2. It originates from insufficient input sanitization and output escaping of the Table Field Value. Authenticated users with subscriber-level access or above can inject arbitrary web scripts that execute when any user views an affected page. The issue is tracked under CWE-79.

Critical Impact

Low-privileged WordPress users (subscribers) can inject persistent JavaScript into pages, enabling session theft, account takeover, and drive-by browser attacks against site visitors and administrators.

Affected Products

  • Table Field Add-on for ACF and SCF (WordPress plugin) — all versions through 1.4.1-RC2
  • Deployments pairing the plugin with Advanced Custom Fields (ACF)
  • Deployments pairing the plugin with Secure Custom Fields (SCF)

Discovery Timeline

  • 2026-10-10 - CVE-2026-96743 published to the National Vulnerability Database
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-96743

Vulnerability Analysis

The vulnerability is a stored (persistent) XSS in the plugin's Table Field feature. User-supplied table cell data is written to the database and later rendered without proper escaping. Any authenticated user above the subscriber threshold can submit crafted payloads containing HTML or JavaScript. When another user — including administrators — loads a page containing the stored table, the injected script runs in that user's browser session. Because the attack vector is network-based and requires no victim interaction beyond visiting the page, exploitation scales across every visitor to the affected content.

Root Cause

The plugin's field handling in classes/Field.php fails to sanitize input before storage and omits output escaping during render. Review of the vulnerable code paths at approximately line 275 and line 463 of the 1.4.0 tag confirms that table values flow to output without functions such as esc_html(), esc_attr(), or wp_kses(). The fix landed in the 1.4.1 release, as shown in the plugin changeset 3732330.

Attack Vector

An attacker registers or compromises any account at subscriber level or higher. Using an interface that accepts Table Field input, the attacker submits a payload containing script tags or event-handler attributes within a table cell value. The malicious content is persisted alongside legitimate table data. Each subsequent page load that renders the table executes the attacker-controlled JavaScript in the victim's browser under the site's origin, enabling cookie theft, forced actions via the WordPress REST API, or redirection to attacker infrastructure.

No verified public exploit code is available. For technical references, see the Wordfence Vulnerability Report and the WordPress Plugin Changeset Comparison.

Detection Methods for CVE-2026-96743

Indicators of Compromise

  • Table Field entries in the WordPress database (wp_postmeta) containing <script>, onerror=, onload=, or javascript: substrings.
  • Unexpected outbound requests from administrator browsers to unfamiliar domains shortly after visiting plugin-rendered pages.
  • Creation of new administrator accounts or REST API privilege changes shortly after subscriber-level logins.
  • Modified or newly created posts containing table fields authored by low-privilege user roles.

Detection Strategies

  • Query wp_postmeta for ACF Table Field keys and flag values containing HTML tags or JavaScript URI schemes.
  • Enable Content Security Policy (CSP) reporting to surface inline script executions on pages rendered by the plugin.
  • Correlate subscriber account activity with content edits touching table fields to identify suspicious authoring patterns.

Monitoring Recommendations

  • Monitor WordPress audit logs for user role creation, metadata changes, and plugin configuration edits by non-privileged accounts.
  • Alert on administrator session anomalies, including concurrent sessions from new IP addresses or geolocations.
  • Track changes to the plugin files under wp-content/plugins/advanced-custom-fields-table-field/ to detect tampering or rollback.

How to Mitigate CVE-2026-96743

Immediate Actions Required

  • Upgrade the Table Field Add-on for ACF and SCF plugin to version 1.4.1 or later.
  • Audit all existing Table Field content for stored HTML or JavaScript payloads and remove malicious entries.
  • Review and tighten WordPress user registration settings; restrict subscriber signup where it is not required.
  • Rotate administrator passwords and invalidate active sessions if subscriber-created content is suspected of containing payloads.

Patch Information

The vendor remediated the issue in version 1.4.1. The fix adds proper sanitization and output escaping to the Table Field handling in classes/Field.php. See the official WordPress Plugin Changeset for the patched code.

Workarounds

  • Temporarily deactivate the Table Field Add-on until the update to 1.4.1 is applied.
  • Restrict the user roles permitted to edit posts or custom fields so that subscriber-level accounts cannot submit Table Field data.
  • Deploy a Web Application Firewall (WAF) rule that blocks requests containing script-like payloads targeting ACF table field parameters.
  • Enforce a strict Content Security Policy that disallows inline scripts on pages rendering plugin content.
bash
# Example WP-CLI commands to inventory and update the vulnerable plugin
wp plugin list --name=advanced-custom-fields-table-field --fields=name,status,version
wp plugin update advanced-custom-fields-table-field --version=1.4.1

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.