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

CVE-2026-57708

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 5 weeks old

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in CRM Perks Contact Form Entries contact-form-entries allows Reflected XSS.This issue affects Contact Form Entries: from n/a through <= 1.5.2.

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

Reflected XSS vulnerability in CRM Perks Contact Form Entries plugin allows attackers to inject malicious JavaScript scripts via unsanitized user input that gets reflected back in web pages. The vulnerability exists in versions up to and including 1.5.2.

MitigationImplement proper input validation and output encoding/escaping for all user-supplied data before reflecting it in HTML responses. Additionally, configure Content Security Policy (CSP) headers to mitigate XSS execution.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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. Locate the CRM Perks Contact Form Entries plugin installation
    Access the WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect the plugin directory at /wp-content/plugins/crm-perks-contact-form-entries/ for the main plugin file
    Affected if The plugin directory or listing exists on the system
  2. Determine the installed version number
    Open the main plugin file (typically contact-form-entries.php) and locate the 'Version' header in the plugin comments, or check the version displayed in the WordPress plugins list
    Affected if The version listed is 1.5.2 or any lower version number (e.g., 1.5.1, 1.5.0, 1.0.0)
  3. Verify the plugin is active
    Check the WordPress plugins page status, or query the wp_options table for option_name='active_plugins' to confirm the plugin is enabled
    Affected if The plugin shows as 'Active' or is present in the active_plugins array
  4. Identify if form submission functionality is accessible
    Test accessing a page containing a contact form built with this plugin, or check if the plugin's shortcode or widget is embedded in any published pages/posts
    Affected if Any contact form created by the plugin is published and accessible to users or attackers

Your environment is affected if CRM Perks Contact Form Entries plugin version 1.5.2 or lower is installed and active, with at least one contact form accessible on the site where user input could be reflected.

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

Implement proper input validation and output encoding/escaping for all user-supplied data before reflecting it in HTML responses. Additionally, configure Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix Low confidence

Latest version of Contact Form Entries plugin (verify version > 1.5.2 in the WordPress plugin repository)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Contact Form Entries' plugin by CRM Perks
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, update to the latest version that includes the security fix
  6. 6. After updating, verify the plugin is functioning correctly and test the contact form submissions
Caveat Minor - XSS patches typically do not introduce breaking changes; review plugin settings after update

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57708 — 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-57708 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