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

CVE-2026-7052

HIGH · 7.2 CVSS v3.1 Published 2026-05-28
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 HT Contact Form – Drag & Drop Form Builder for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'file_upload' parameter in all versions up to, and including, 2.8.2 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. Exploitation requires the 'Store Submissions' setting to be enabled, as this controls whether unsanitized field values are persisted to the database and subsequently rendered via dangerouslySetInnerHTML in the admin entry viewer.

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 HT Contact Form plugin versions up to 2.8.2 have a stored XSS vulnerability in the 'file_upload' parameter. Unauthenticated attackers can inject malicious JavaScript through form submissions when the 'Store Submissions' setting is enabled. The injected scripts execute in the admin panel when viewing submissions because the plugin uses dangerouslySetInnerHTML to render unsanitized field values from the database.

MitigationUpdate the plugin to a version beyond 2.8.2 when available, or disable the 'Store Submissions' setting as a temporary workaround. The fix requires implementing proper input sanitization for all form fields and replacing dangerouslySetInnerHTML with safe output escaping.

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. Check installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins, find 'HT Contact Form' and note the version number displayed, or inspect the plugin's main PHP file for the 'Version' header comment
    Affected if Version is 2.8.2 or lower
  2. Verify Store Submissions setting status
    Go to the plugin settings page in WordPress admin (usually under Settings > HT Contact Form or a dedicated settings menu), locate the 'Store Submissions' or 'Save form submissions' toggle/checkbox, and note whether it is enabled
    Affected if The Store Submissions setting is turned ON (enabled)
  3. Inspect database for stored submissions
    Access the WordPress database (via phpMyAdmin or CLI), locate the plugin's submissions table (commonly named wp_htcf_submissions, wp_ht_contact_form_submissions, or similar pattern), and query for any submitted records containing the file_upload field
    Affected if Any submissions exist in the database with a file_upload value present

Your environment is affected if the plugin version is 2.8.2 or lower AND the Store Submissions setting is enabled AND any form submissions with file_upload data have been stored in the database.

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 a version beyond 2.8.2 when available, or disable the 'Store Submissions' setting as a temporary workaround. The fix requires implementing proper input sanitization for all form fields and replacing dangerouslySetInnerHTML with safe output escaping.

Recommended fix Moderate confidence

Latest version of HT Contact Form plugin (version 2.8.3 or higher)

  1. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  2. Locate 'HT Contact Form – Drag & Drop Form Builder for WordPress' plugin
  3. Check the current installed version (should be 2.8.2 or below based on CVE description)
  4. Update the plugin to the latest available version from the WordPress plugin repository
  5. After updating, verify the 'Store Submissions' setting in plugin configuration - consider disabling it if not required for business logic, as this is the attack vector enabler
  6. Test that form submissions work correctly after the update
Caveat Review changelog for any breaking changes between your current version and the latest release

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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