Contact FormWordPress extension · Fluentforms
CVE-2024-4709
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Contact Form Plugin by Fluent Forms for Quiz, Survey, and Drag & Drop WP Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘subject’ parameter in versions up to, and including, 5.1.16 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level permissions and above, and access granted by an administrator, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Fluent Forms WordPress plugin versions up to 5.1.16 fails to properly sanitize and escape the 'subject' parameter, allowing authenticated users with contributor-level permissions or higher to inject malicious JavaScript code. This stored XSS payload executes whenever users access pages containing the injected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Contact FormWordPress extension
< 5.1.17CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Fluent Forms plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and locate 'Fluent Forms'. Note the installed version number displayed.Affected if The plugin is installed and the version shown is lower than 5.1.17 (for example, 5.1.16, 5.1.15, etc.)
-
Confirm user role permissionsNavigate to Users > All Users in WordPress admin. Review the roles assigned to each user. Check if any users have 'Contributor', 'Author', or 'Editor' roles.Affected if Non-administrator users with Contributor-level access or higher exist and have permission to create or edit forms.
-
Check form creation accessGo to Fluent Forms > Forms. Attempt to access or create a form using a limited user account (Contributor level), or review whether form creation is restricted to Administrators only.Affected if Users with Contributor, Author, or Editor roles can access the form builder functionality.
-
Inspect existing form subjects for injection pointsReview existing forms in Fluent Forms > Forms. Examine the form settings, particularly the email notification 'subject' field and any frontend-facing form titles or headers.Affected if Forms contain user-supplied subject values that may contain unsanitized content and are visible to other users or visitors.
Your environment is affected if Fluent Forms plugin version is below 5.1.17 AND non-administrator users with Contributor-level permissions or higher can access form creation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.1.17
Update the Fluent Forms plugin to the latest version which includes proper input sanitization and output escaping for the subject parameter. If immediate update is not possible, restrict form creation permissions to administrator-level users only until the patch can be applied.
Fluent Forms plugin version 5.1.17
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the 'Fluent Forms' plugin (Contact Form Plugin by Fluent Forms for Quiz, Survey, and Drag & Drop WP Form Builder)
- Click 'Update now' to upgrade to version 5.1.17 or later
- Verify the plugin version after update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Contact Form
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4709 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-4709 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data