Forminator Security Update Checklist: August 2026 CVEs
August 18, 2026
Sites using the Forminator WordPress plugin should update to version 1.57.0.3 or later, with the current WordPress.org release preferred. The National Vulnerability Database published high-severity records for CVE-2026-18323 and CVE-2026-18328 during the August 25 review window. Their official WordPress.org release-history references map the fixes to Forminator 1.57.0.3 and 1.57.0.1 respectively. The earlier CVE-2026-15748 fix remains part of the same supported maintenance path.
WordPress.org currently lists Forminator 1.57.1. Updating to that current supported release, reviewing access, and checking the site after maintenance is the practical response. This is a defender-focused guide: it covers the approved update path and normal business checks without technical attack detail.
Who should update
- Sites running Forminator 1.57.0.2 or an earlier release.
- Organizations using public contact, application, registration, payment, quiz, or other Forminator forms.
- Managed WordPress customers whose host or agency maintains plugins on their behalf.
Update Forminator safely
- In WordPress, open Plugins and confirm whether Forminator is installed and active.
- Use the site’s normal approved maintenance and recovery process. Do not create or alter a backup schedule solely for this update.
- Update Forminator to 1.57.0.3 or later through the normal WordPress update workflow. Prefer the current WordPress.org release when it is compatible with the site.
- Keep WordPress core, the active theme, and connected payment, email, or form extensions current.
- Review WordPress administrator and form-management access so only trusted staff retain the permissions they need.
Verify forms after maintenance
- Confirm the installed Forminator version is 1.57.0.3 or later.
- Have an authorized site owner submit a representative public form using the site’s normal test policy.
- Confirm approved confirmation, notification, moderation, and payment workflows still work as intended.
- Review normal WordPress and hosting security telemetry for unexpected form errors, unfamiliar administrator accounts, or unexpected executable files. Investigate confirmed issues through the site’s approved incident process.
For managed WordPress and hosting teams
Record the maintenance window, fixed version, affected sites, reviewer, and verification result. For shared-hosting environments, confirm the update did not change scheduled task, mail, payment, or cache behavior. Keep the customer-facing maintenance notice factual: the plugin was updated, normal form and payment checks passed, and a team contact is available for follow-up.
Related Fix I.T. Phill help
- WordPress support for help with plugin maintenance, forms, themes, and site-owner troubleshooting.
- WHM and cPanel support for managed hosting maintenance and safe post-update checks.
- How to add a WordPress security plugin for broader site-hardening guidance.
- Earlier Forminator CVE-2026-6214 guidance for the related historical patch record.

