AI Builder permits contributor stored JavaScript
AI Builder before 2.7.8 lets Contributors save custom JavaScript against a post and echoes that value inside a script tag on the front end without adequate sanitization. The injected code executes for visitors and for Editors or Administrators who review the post. The authoritative export does not name the save endpoint, parameter, or rendering function.
- Component
- AI Builder
- Plugin slug
ai-builder- Affected
- 2.4.1 to < 2.7.8
- Safe version
2.7.8- Published
- Sep 11, 2026
This CVE was published Sep 11, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update AI Builder to 2.7.8 or later. The authoritative export marks versions below 2.7.8 affected. The application-level fix must prevent untrusted roles from storing executable JavaScript and must encode any retained value for its precise script context before output.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The AI Builder WordPress plugin before 2.7.8 does not sanitise custom JavaScript saved against a post before echoing it inside a script tag on the front end, allowing users with contributor level access and above to store arbitrary JavaScript that will execute in the browser of anyone who views the post, including the editor or administrator who reviews it.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H