Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-93303 Overview
CVE-2026-93303 is a Stored DOM-Based Cross-Site Scripting (XSS) vulnerability in the HT Contact Form – Drag & Drop Form Builder for WordPress plugin. The flaw affects all versions up to and including 2.10.1. It stems from insufficient input sanitization and output escaping in the form_data Rich Text Field processed through the plugin's Draft Save/Resume workflow. Unauthenticated attackers can inject arbitrary JavaScript that executes in the browser of any user who visits an attacker-supplied draft resume URL. The exploit chain abuses the draft_key and access_token values returned directly in the save response, which the attacker uses to construct the malicious link. The weakness is classified under CWE-79.
Critical Impact
Unauthenticated attackers can execute arbitrary JavaScript in a victim's browser session, enabling session theft, credential harvesting, and account takeover against WordPress site visitors and administrators.
Affected Products
- HT Contact Form – Drag & Drop Form Builder for WordPress plugin, all versions through 2.10.1
- WordPress sites using the vulnerable plugin with Draft Save/Resume functionality enabled
- End users and administrators who interact with attacker-crafted draft resume URLs
Discovery Timeline
- 2026-09-25 - CVE-2026-93303 published to NVD
- 2026-09-25 - Last updated in NVD database
Technical Details for CVE-2026-93303
Vulnerability Analysis
The HT Contact Form plugin exposes REST endpoints under admin/Includes/Api/Endpoints/Draft.php that permit unauthenticated callers to save and resume form drafts. When a Rich Text Field is submitted inside the form_data payload, the plugin stores the raw HTML without applying sufficient sanitization. On resume, the stored content is rendered into the DOM by client-side JavaScript in assets/js/form.js, where it is interpreted as live markup rather than inert text. Because the save endpoint returns the generated draft_key and access_token directly to the caller, an attacker can craft a resume URL that reliably serves the injected payload to any victim who follows the link.
Root Cause
The root cause is the combination of two issues: missing server-side sanitization of Rich Text Field content before persistence in the Drafts model (admin/Includes/Models/Drafts.php), and unescaped DOM insertion of that content during draft resume in the plugin's JavaScript. The shortcode rendering path in include/UI/ShortCode.php also contributes by trusting the stored payload. Because draft creation requires no authentication and the response surfaces the tokens needed to retrieve the draft, the attacker controls the full lifecycle of the stored payload.
Attack Vector
An unauthenticated attacker submits a draft containing a malicious Rich Text Field payload to the plugin's draft save endpoint. The server responds with the draft_key and access_token, which the attacker combines into a resume URL. The attacker then distributes the URL through phishing, forum posts, or search-engine poisoning. When a victim clicks the link, the stored JavaScript executes in the victim's browser under the WordPress site's origin, enabling cookie theft, forced actions on behalf of the user, redirection to attacker infrastructure, or injection of secondary payloads. The scope change (S:C) reflects that script executed in the site origin can affect resources beyond the plugin itself.
See the Wordfence Vulnerability Intelligence Report and the WordPress Plugin Draft Endpoint Code for the vulnerable code paths.
Detection Methods for CVE-2026-93303
Indicators of Compromise
- Unexpected POST requests to the plugin's draft save REST endpoint from unauthenticated clients, especially from unfamiliar IP ranges or automated user agents.
- Draft records in the plugin's storage containing <script>, onerror=, onload=, javascript: URIs, or encoded variants inside Rich Text Field values.
- Outbound requests from visitor browsers to unknown third-party domains originating from pages that render HT Contact Form drafts.
- Resume URLs in referrer logs that contain draft_key and access_token parameters followed by anomalous session or admin activity.
Detection Strategies
- Inspect WordPress database tables used by the plugin for stored draft content and grep for HTML event handlers and script tags.
- Enable web application firewall rules that flag draft save requests containing executable HTML or JavaScript patterns in form_data.
- Correlate access logs for draft resume URLs against subsequent authenticated admin actions to detect session abuse chains.
Monitoring Recommendations
- Monitor REST API traffic to /wp-json/ paths associated with the HT Contact Form plugin for abnormal volume or unauthenticated writes.
- Alert on administrator account activity that follows a visit to a draft resume URL within a short time window.
- Review Content Security Policy violation reports for inline-script or event-handler violations originating on pages that embed the plugin.
How to Mitigate CVE-2026-93303
Immediate Actions Required
- Upgrade the HT Contact Form – Drag & Drop Form Builder plugin to a release later than 2.10.1 once the vendor publishes a fixed version.
- Audit existing draft records and delete any entries containing script tags, event handlers, or suspicious HTML in Rich Text Fields.
- Rotate administrator session cookies and reset credentials for any user who may have clicked a draft resume URL.
Patch Information
Review the vendor's remediation in the WordPress Plugin ChangeSet Review and consult the Wordfence Vulnerability Intelligence Report for the fixed version and upgrade guidance. Apply the plugin update through the WordPress admin console or via WP-CLI, then verify the installed version matches the patched release.
Workarounds
- Deactivate the HT Contact Form plugin until a patched version is installed if the Draft Save/Resume feature is in use.
- Deploy a WordPress-aware web application firewall rule that blocks unauthenticated POSTs to the plugin's draft endpoints or strips script content from form_data payloads.
- Enforce a strict Content Security Policy that disallows inline scripts and limits script sources to trusted origins, reducing the impact of injected markup.
# Configuration example: disable the plugin via WP-CLI until patched
wp plugin deactivate ht-contactform
wp plugin status ht-contactform
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

