Contact FormWordPress extension · Fluentforms
CVE-2023-6957
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 Fluent Forms plugin for WordPress by Fluent Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 5.1.9 due to insufficient input sanitization and output escaping. This makes it possible for attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploitation level depends on who is granted the right to create forms by an administrator. This level can be as low as contributor, but by default is admin.
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 confidenceStored Cross-Site Scripting vulnerability in Fluent Forms WordPress plugin (versions up to 5.1.9). Attackers with form creation privileges (as low as contributor) can inject malicious scripts through insufficiently sanitized form inputs. These scripts execute when users access pages displaying the unsanitized 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.10CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or check the /wp-content/plugins/fluentform/ directory for the fluentform.php file and read its header for version infoAffected if Plugin is present and version is below 5.1.10
-
Confirm installed version against affected rangeOpen the plugin file fluentform.php and locate the 'Version' header comment, or check in WordPress admin under Plugins listAffected if Version is less than 5.1.10 (e.g., 5.1.9, 5.1.8, etc.)
-
Identify users with form creation privilegesGo to WordPress admin > Users > Roles, or check if contributor-level users have access to Fluent Forms > Forms menu. Review which user accounts have 'fluentform_forms' capabilityAffected if Users with contributor role or higher can create or edit forms
-
Inspect stored form entries for malicious scriptsIn WordPress admin, go to Fluent Forms > All Forms, then view entries for each form. Check input values for suspicious patterns like <script>, javascript:, onload=, or other HTML/script tagsAffected if Any form entries contain unsanitized HTML, script tags, or event handlers like onerror, onload
-
Review form field settings for sanitizationEdit a form in Fluent Forms builder, check each input field's settings for any custom code or shortcode fields, and verify if raw HTML is being rendered in form notifications or confirmationsAffected if Form fields are configured to render raw HTML or custom code without sanitization
User is affected if Fluent Forms plugin version is below 5.1.10 AND users with contributor-level access can create forms AND unsanitized form entries exist in the system
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.10
Update Fluent Forms plugin to version beyond 5.1.9; until patched, restrict form creation privileges to highly trusted users only.
Fluent Forms 5.1.10
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the Fluent Forms plugin in the list
- Click 'Update now' if an update is available, or manually update to version 5.1.10
- Verify the update completed successfully by checking the plugin version
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
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6957 — 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-2023-6957 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