CVE-2026-96743 json
Table Field Add-on for ACF and SCF <= 1.4.1-RC2 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Table Field Value
published 2026-10-10 30 d ago modified 2026-10-13 27 d ago also EUVD-2026-96036
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
The Table Field Add-on for ACF and SCF plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Table Field Value in all versions up to, and including, 1.4.1-RC2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 29 d ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
Affected products
- jonua Table Field Add-on for ACF and SCF
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/2656ae60-0658-4230-99fc-9a754a4f61bf?source=cve
- plugins.trac.wordpress.org /browser/advanced-custom-fields-table-field/tags/1.4.0/classes/Field.php#L275
- plugins.trac.wordpress.org /browser/advanced-custom-fields-table-field/tags/1.4.0/classes/Field.php#L463
- plugins.trac.wordpress.org /changeset/3732330/advanced-custom-fields-table-field/trunk/classes/Field.php
- plugins.trac.wordpress.org /changeset?reponame=&new=3732282%40advanced-custom-fields-table-field%2Ftags%2F1.4.1&old=3696309%40advanced-cu
Sources
- CVE List CVE-2026-96743
- NVD CVE-2026-96743
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.