CVE-2026-6048
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 · uneditedThe Flipbox Addon for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Flipbox widget's button URL `custom_attributes` field in all versions up to, and including, 2.1.1 due to insufficient validation of custom attribute names. Specifically, the plugin uses `esc_html()` on the attribute name which does not prevent event handler attributes (e.g., `onmouseover`, `onclick`). This makes it possible for authenticated attackers, with author-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 confidenceThe Flipbox Addon for Elementor plugin for WordPress is vulnerable to Stored XSS via the Flipbox widget's button URL custom_attributes field. The plugin uses esc_html() to sanitize attribute names, but this function doesn't prevent event handler attributes like onmouseover or onclick from being injected. Authenticated attackers with author-level access can inject malicious scripts that execute when users view affected pages.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Flipbox Addon for Elementor is installedCheck the WordPress plugins directory or review the site's plugin list for 'Flipbox Addon for Elementor' or similar flipbox/elementor addon pluginsAffected if The plugin is present on the WordPress site
-
Identify Flipbox widgets in useSearch page content, Elementor templates, or the database for instances of the flipbox widget, particularly those with button URL custom_attributes fields configuredAffected if Any Flipbox widget with custom_attributes configured is present
-
Inspect custom_attributes for dangerous tagsExamine the custom_attributes field values in the widget settings or database entries. Look for attribute names containing event handlers such as onmouseover, onclick, onload, onerror, or onfocusAffected if The custom_attributes field contains attribute names that are event handler attributes (onmouseover, onclick, etc.)
-
Check user role permissionsReview which user roles have access to edit Elementor pages containing Flipbox widgets. Determine if any author-level or higher users exist on the siteAffected if Author-level or higher users have access to edit pages with Flipbox widgets containing custom_attributes
The site is affected if the Flipbox Addon for Elementor plugin is installed and contains Flipbox widgets with custom_attributes that include event handler attribute names like onmouseover or onclick.
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 the Flipbox Addon for Elementor plugin when available, or disable the plugin until a patch is released. If immediate remediation is required and no patch exists, consider removing or restricting access to the custom_attributes functionality.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6048 — 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-6048 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