CVE-2026-96813 10web CVE debrief

Who should care

Defenders responsible for WordPress deployments using the Form Maker plugin should assess exposure and prioritize verification and updates to prevent potential exploitation. This includes operators managing affected deployments, platform administrators, vulnerability management teams, and security teams that need to verify and update the plugin, assess exposure, and monitor for potential exploitation attempts.

Why it matters

CVE-2026-96813 is a Stored Cross-Site Scripting vulnerability in the Form Maker by 10Web WordPress plugin. Defenders should prioritize verifying and updating the plugin, assessing exposure in their WordPress deployments, and monitoring for potential exploitation attempts. The vulnerability allows unauthenticated attackers to inject arbitrary web scripts, which execute when a user accesses an injected page. Affected versions require verification, and remediation involves updating to a patched version.

• Unauthenticated attackers can inject arbitrary web scripts
• Injected scripts execute when a user accesses an injected page
• Defenders must verify and update the Form Maker plugin
• Exposure assessment is required for WordPress deployments

Technical summary

The Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Mark on Map Longitude/Latitude Fields in all versions up to, and including, 1.15.47. This is due to insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Defensive priority

Defenders should prioritize verifying and updating the Form Maker plugin to a patched version, assessing exposure in their WordPress deployments, and monitoring for potential exploitation attempts.

Recommended defensive actions

• Verify and update the Form Maker plugin to a patched version
• Assess exposure in WordPress deployments
• Monitor for potential exploitation attempts
• 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 entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the corpus does not establish versions beyond 1.15.47, exploitation, impact, or remediation, which require verification from the supplied official sources.

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.