CVE-2026-85678 WordPress.org CVE debrief

Who should care

Defenders responsible for WordPress installations with the AI Builder plugin, and users with contributor level access and above, should assess exposure and prioritize updating the plugin.

Why it matters

Defenders should prioritize verifying and updating the AI Builder WordPress plugin to prevent arbitrary JavaScript execution. Users with contributor level access and above can store malicious JavaScript, impacting anyone who views the post.

• Arbitrary JavaScript execution in browsers of users viewing affected posts
• Potential for malicious JavaScript to be stored and executed
• Need for verification and updates to the AI Builder WordPress plugin

Technical summary

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. This vulnerability allows for potential malicious JavaScript execution, impacting users viewing affected posts and requiring verification and updates to the plugin.

Defensive priority

Defenders should prioritize verifying and updating the AI Builder WordPress plugin to version 2.7.8 or later, and assess exposure for users with contributor level access and above.

Recommended defensive actions

• Verify and update the AI Builder WordPress plugin to version 2.7.8 or later
• Assess exposure for users with contributor level access and above
• Monitor for suspicious JavaScript activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability, but do not offer additional context or affected versions beyond the plugin version 2.7.8. Defenders should verify plugin versions and configurations, assess exposure for users with contributor level access and above, and monitor for suspicious JavaScript activity. Limited source detail suggests verifying plugin updates and configurations.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.