CVE-2026-32532
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in ThemeHunk Contact Form & Lead Form Elementor Builder lead-form-builder allows Stored XSS.This issue affects Contact Form & Lead Form Elementor Builder: from n/a through <= 2.0.1.
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 · moderate confidenceStored XSS vulnerability in ThemeHunk Contact Form & Lead Form Elementor Builder plugin allows attackers to inject malicious JavaScript through form fields. The payload persists in the database and executes when administrators or other users view form submissions or entries in the WordPress admin dashboard.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedGo to WordPress admin > Plugins and look for 'ThemeHunk Contact Form & Lead Form Elementor Builder' in the installed plugins listAffected if the plugin appears in the plugins list and is activated
-
Check the installed versionIn Plugins list, click on the plugin to view details, or check the plugin header in /wp-content/plugins/ directory for the version numberAffected if the version is earlier than the latest patched version (contact the vendor or check WordPress plugin repository for current patched version)
-
Inspect form entries for suspicious contentAccess the plugin's form submissions area in WordPress admin (usually under 'ThemeHunk' menu or 'Forms' > 'Entries'). Look for form submissions containing <script>, javascript:, onload, onerror, or other HTML/script tags in text fieldsAffected if any form entries contain raw HTML, script tags, or JavaScript event handlers like onerror or onload in input fields
-
Check browser console for XSS while viewing entriesAs an administrator, navigate to the form submissions area in the admin dashboard and open browser developer tools (F12). Check the Console tab for any JavaScript errors or executed scripts while viewing form entriesAffected if JavaScript executes or errors appear in the console when viewing form submission data
A user is affected if the ThemeHunk Contact Form plugin is active, the version is unpatched, AND malicious form submissions exist in the database that could execute when viewed by admins
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.
From vendor dataUpdate to the latest patched version of the plugin when available. Until then, review all form submissions carefully and limit admin access to trusted personnel only.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32532 — 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-32532 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