CVE-2026-6828
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 – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'permission_message' parameter in all versions up to, and including, 6.2.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, 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 fails to properly sanitize and escape the 'permission_message' parameter, allowing authenticated users with contributor-level access or higher to inject malicious JavaScript. This stored XSS payload executes whenever users access pages containing the affected form, enabling session hijacking, credential theft, or defacement.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 installedNavigate to WordPress admin > Plugins and check if 'Fluent Forms' appears in the installed plugins list, or query the wp_options table for option_name = 'fluentform_version'Affected if Fluent Forms plugin is not present in the WordPress installation
-
Check the installed Fluent Forms versionIn WordPress admin, go to Plugins > Fluent Forms and view the version number, or query: SELECT option_value FROM wp_options WHERE option_name = 'fluentform_version'Affected if The installed version is lower than 6.2.2 (e.g., 6.2.1, 6.2.0, earlier versions)
-
Identify forms using the permission_message fieldQuery the wp_fluentform_forms table for records containing the permission_message field: SELECT id, form_title FROM wp_fluentform_forms WHERE form_json LIKE '%permission_message%'Affected if Any forms exist that utilize the permission_message setting
-
Inspect permission_message field values for XSS payloadsExamine the permission_message content in the form configuration for suspicious patterns: SELECT form_json FROM wp_fluentform_forms WHERE form_json LIKE '%permission_message%' and look for script tags, event handlers (onclick, onerror, etc.), or encoded JavaScriptAffected if The permission_message field contains unsanitized HTML, script tags, or JavaScript event handlers
-
Check for recently created or modified forms by contributor-level usersQuery wp_posts and wp_postmeta for form entries created by users with contributor role (typically user_level < 5 or role = 'contributor') around the time of suspected exploitationAffected if Forms were created or modified by contributor-level users without admin review
You are affected if Fluent Forms version is below 6.2.2 AND forms utilizing the permission_message field exist with injected malicious scripts or suspicious HTML/JavaScript content.
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 · scopedUpgrade to version 6.2.2 or later. If immediate patching is not possible, restrict contributor-level user permissions and review forms using the permission_message field for existing malicious content.
Fluent Forms version greater than 6.2.1 (latest available version)
- 1. Backup your WordPress site and database before making any changes
- 2. Navigate to the WordPress admin dashboard
- 3. Go to Plugins > Installed Plugins
- 4. Find 'Fluent Forms' in the plugin list
- 5. If an update is available, click 'Update Now' to install the latest version
- 6. Alternatively, you can manually download the updated plugin from the WordPress plugin repository
- 7. After updating, verify the 'permission_message' field in form settings is now properly sanitized
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6828 — 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-2026-6828 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