CVE-2026-4077
Stored XSS in Ecover Builder For Dummies WordPress Plugin
Publication date: 2026-03-21
Last updated on: 2026-03-21
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ecover_builder_for_dummies | ecover_builder_for_dummies | to 1.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Ecover Builder For Dummies plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in the 'id' parameter of the 'ecover' shortcode. This vulnerability exists in all versions up to and including 1.0. It occurs because the plugin does not properly sanitize or escape user input supplied to the 'id' attribute of the shortcode.
As a result, authenticated users with Contributor-level access or higher can inject malicious scripts into pages. These scripts will execute whenever any user accesses the affected page.
How can this vulnerability impact me? :
This vulnerability can allow attackers with Contributor-level access or above to inject arbitrary web scripts into pages. These scripts can execute in the context of users visiting those pages, potentially leading to theft of user credentials, session hijacking, defacement, or other malicious actions.
Since the attack requires authenticated access, it may be limited to insiders or users with some level of trust, but the impact can still be significant as it affects all users who view the injected content.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know