dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-8901

HIGH · 7.2 CVSS v3.1 Published 2026-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The Integration for Freshsales – Contact Form 7, WPForms, Elementor, Gravity Forms and More plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Form Submission Data in all versions up to, and including, 1.0.15 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload only executes when a CRM API call fails for the submitted form and an administrator subsequently views the error log details modal in the WordPress admin panel.

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 confidence

The Freshsales integration plugin for WordPress fails to sanitize form submission data before storage and does not escape this data when displaying error logs in the admin panel. Unauthenticated attackers can submit forms with malicious JavaScript payloads. The payload executes only when a CRM API call fails and an administrator views the error log details modal, making this a stored XSS requiring administrative interaction.

MitigationUpdate the plugin to version 1.0.16 or later. Until a patch is available, restrict form submission access or disable the Freshsales integration if possible, and monitor admin panels for suspicious error log entries.

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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Freshsales plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Freshsales' or 'Freshsales integration' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'freshsales' or similar.
    Affected if The plugin appears in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, click on the Freshsales plugin to view its details, or check the plugin's main PHP file for the 'Version' header in the plugin comment block. Compare the version number to 1.0.15.
    Affected if The installed version is 1.0.15 or lower
  3. Verify form-to-CRM integration is active
    Navigate to the Freshsales plugin settings page in WordPress admin. Look for options related to form submissions, CRM sync, or API configuration. Check if any forms are configured to send data to the Freshsales CRM.
    Affected if Form submissions to Freshsales CRM are enabled and configured with API credentials
  4. Inspect error logs for suspicious content
    In the WordPress admin panel, access the Freshsales plugin error log or logs viewer. Look for any error entries that contain JavaScript code, <script> tags, or unusual HTML attributes in the error details fields.
    Affected if Error logs contain unescaped HTML or script content from form submissions

A user is affected if the Freshsales plugin version is 1.0.15 or lower AND form-to-CRM integration is actively configured, since the stored XSS executes only when an admin views failed API call error logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.0.16 or later. Until a patch is available, restrict form submission access or disable the Freshsales integration if possible, and monitor admin panels for suspicious error log entries.

Recommended fix Moderate confidence

Version 1.0.16 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Integration for Freshsales' plugin
  4. 4. Check the current version installed (should be 1.0.15 or below)
  5. 5. If an update is available, click 'Update Now' to update to version 1.0.16 or later
  6. 6. Alternatively, download the latest version from the WordPress plugin repository and upload manually via Plugins > Add New > Upload Plugin
  7. 7. Verify the update was successful by checking the plugin version after updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8901 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8901 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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