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

CVE-2026-4077

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-21
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 Ecover Builder For Dummies plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id' parameter of the 'ecover' shortcode in all versions up to and including 1.0. This is due to insufficient input sanitization and output escaping on the user-supplied 'id' shortcode attribute. 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 Ecover Builder For Dummies WordPress plugin fails to sanitize the 'id' attribute of its 'ecover' shortcode and does not escape output when rendering this attribute, allowing stored XSS injection. An authenticated attacker with Contributor-level permissions can insert malicious JavaScript via the shortcode that executes when other users view affected pages.

MitigationUpdate to the latest version of the plugin which implements proper input sanitization and output escaping for the 'id' shortcode parameter. Until a patch is available, restrict shortcode usage permissions to trusted roles.

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. Verify the plugin is installed
    Check the WordPress plugins directory orwp-content/plugins/ for a folder named 'ecover-builder-for-dummies' or similar. In WordPress admin, go to Plugins > Installed Plugins and look for 'Ecover Builder For Dummies'.
    Affected if The plugin is installed and active in WordPress
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Ecover Builder For Dummies and view the version number displayed. Alternatively, check the main plugin PHP file header for 'Version:' comment.
    Affected if The installed version has not yet received the patch for proper input sanitization (compare your version against any later releases that address this issue)
  3. Detect usage of the ecover shortcode in content
    Query the WordPress database: SELECT * FROM wp_posts WHERE post_content LIKE '%[ecover%' AND post_status IN ('publish','future','draft'); Adjust wp_ prefix if your installation uses a different table prefix.
    Affected if The shortcode is present in published content, allowing injected scripts to execute when users view those pages
  4. Check for unescaped id attribute rendering
    Temporarily create a test page with [ecover id='"><script>alert(1)</script>'] shortcode and view the page source. Search for the literal script tags or unescaped quotes in the rendered HTML output.
    Affected if The id parameter value appears unescaped in the HTML output (you see > or < characters rather than &gt; or &lt;)
  5. Identify users with Contributor-level access
    In WordPress admin, go to Users and review the Role column. Contributors can create posts but cannot publish without approval. Query: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%contributor%';
    Affected if One or more Contributor-level users exist, meaning they have permission to insert the malicious shortcode

Your environment is affected if the Ecover Builder For Dummies plugin is installed, the ecover shortcode is used in published content, and users with Contributor or higher roles exist who could inject the unsanitized id attribute.

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 to the latest version of the plugin which implements proper input sanitization and output escaping for the 'id' shortcode parameter. Until a patch is available, restrict shortcode usage permissions to trusted roles.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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