CVE-2026-32411
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 Simpma Embed Calendly embed-calendly-scheduling allows Stored XSS.This issue affects Embed Calendly: from n/a through <= 4.4.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the Embed Calendly plugin (version <= 4.4) by Simpma. The plugin fails to properly sanitize or encode user input when embedding Calendly scheduling widgets, allowing attackers to inject malicious JavaScript that persists on the server and executes in victims' browsers when they view pages containing the embedded calendar.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify if Embed Calendly plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Embed Calendly' by Simpma. Alternatively, check the plugin directory (wp-content/plugins) for a folder named 'embed-calendly' or similar.Affected if The plugin is present on the site
-
Determine the installed plugin versionIn WordPress admin > Plugins > Installed Plugins, click on the Embed Calendly plugin to view its details, or open the main plugin PHP file and look for the 'Version' header in the plugin comments.Affected if The version number is 4.4 or lower
-
Check for active Calendly embeds on the siteSearch your WordPress database for posts/pages containing 'calendly.com' URLs in the post_content table, or use the WordPress block editor/Gutenberg to search for Calendly embed blocks.Affected if The site has pages or posts with embedded Calendly widgets using this plugin
-
Inspect embedded Calendly URLs for malicious payloadsExamine the stored Calendly embed URLs or iframe code in the affected posts/pages. Look for unusual characters, script tags, or JavaScript event handlers (like onerror, onload) within the URL parameters.Affected if The embedded Calendly URLs contain unexpected script injections, encoded characters, or XSS payloads in the query parameters
A user is affected if the Embed Calendly plugin (version 4.4 or lower) is installed AND the site contains stored XSS payloads in Calendly embed configurations.
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 version of Embed Calendly if a patch is available. Otherwise, implement proper input validation and output encoding on the plugin's input fields, and consider adding Content-Security-Policy headers to mitigate XSS execution.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32411 — 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-32411 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