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

CVE-2026-0868

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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 EMC – Easily Embed Calendly Scheduling Features plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's calendly shortcode in all versions up to, and including, 4.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 EMC WordPress plugin fails to sanitize and escape user-supplied attributes in its calendly shortcode, allowing authenticated contributors+ to inject malicious JavaScript that persists in page content and executes when users view those pages.

MitigationUpdate the plugin to a version beyond 4.4 that properly sanitizes shortcode input and escapes output, or audit and remove any calendly shortcodes from published content until patched.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify if the EMC WordPress plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for a plugin with 'EMC' in the name. Alternatively, check the /wp-content/plugins/ directory for folders containing 'emc' in the name.
    Affected if The plugin is present and its version falls within the vulnerable version range (versions prior to the patched version beyond 4.4)
  2. Retrieve the installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, click on the plugin name to view its details, or inspect the plugin's main PHP file for a 'Version' header comment.
    Affected if The version number is lower than the patched version (which is beyond 4.4)
  3. Search for calendly shortcode usage in database content
    Query the wp_posts table in the WordPress database for posts containing '[calendly' or 'calendly_' in the post_content field. You can use: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%[calendly%';
    Affected if Any posts or pages contain the calendly shortcode, creating potential storage locations for injected malicious scripts
  4. Inspect shortcode attributes for unsanitized content
    Examine the content of posts containing the calendly shortcode. Look for unusual attribute values, especially those containing javascript:, onload=, or script tags within shortcode parameters.
    Affected if The shortcode contains unexpected attribute values suggesting script injection, such as quotes beginning with javascript: or event handlers like onerror=
  5. Review contributor-level user accounts
    In WordPress admin, go to Users > All Users and filter by the 'Contributor' role. Also check wp_usermeta table for users with wp_capabilities containing 'contributor'.
    Affected if There are contributor or higher-level users who could have authored malicious shortcode content

Your environment is affected if the EMC plugin is installed with a version at or below 4.4 and any pages contain the calendly shortcode, particularly if contributor-level accounts exist who may have injected malicious scripts.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 4.4 that properly sanitizes shortcode input and escapes output, or audit and remove any calendly shortcodes from published content until patched.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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