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

CVE-2026-42410

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in CodexThemes TheGem Theme Elements (for Elementor) allows DOM-Based XSS.This issue affects TheGem Theme Elements (for Elementor): from n/a before 5.12.1.1.

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 confidence

DOM-based Cross-site Scripting (XSS) vulnerability in TheGem Theme Elements for Elementor. The vulnerability allows attackers to inject malicious JavaScript through improper handling of user input that gets executed in the victim's browser via DOM manipulation.

MitigationUpdate TheGem Theme Elements (for Elementor) to version 5.12.1.1 or later to remediate this vulnerability.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate TheGem Theme Elements installation
    Check your WordPress plugins/themes directory for 'thegem-elements-elementor' folder or look in WordPress admin under Plugins > Installed Plugins for 'TheGem Theme Elements'
    Affected if The plugin or theme is installed on the WordPress site
  2. Identify installed version
    In WordPress admin, go to Plugins > Installed Plugins and find TheGem Theme Elements. The version number is displayed beneath the plugin name. Alternatively, check the main plugin file (usually thegem-elements-elementor.php) for the 'Version' header.
    Affected if Version is present but below 5.12.1.1
  3. Confirm Elementor is active
    In WordPress admin, verify that Elementor Page Builder plugin is installed and active. The vulnerability affects TheGem Theme Elements 'for Elementor', so Elementor must be running.
    Affected if Elementor is active and TheGem Theme Elements version is below 5.12.1.1
  4. Check for vulnerable input handling
    Inspect any custom widgets or TheGem elements that accept user input (search bars, form fields, text inputs) by viewing page source or using browser dev tools. Look for JavaScript that directly manipulates the DOM with user-supplied data without sanitization.
    Affected if The site uses TheGem widgets with unsanitized user input that gets rendered to the DOM

The environment is affected if TheGem Theme Elements for Elementor is installed with a version lower than 5.12.1.1 and the site uses Elementor with TheGem widgets that handle user input.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update TheGem Theme Elements (for Elementor) to version 5.12.1.1 or later to remediate this vulnerability.

Recommended fix Moderate confidence

5.12.1.1 or later

  1. 1. Log in to the WordPress admin dashboard where TheGem Theme Elements (for Elementor) is installed
  2. 2. Navigate to Plugins or Theme settings to check the current installed version of TheGem Theme Elements
  3. 3. Create a full backup of the WordPress site (database and files) before performing any updates
  4. 4. Update TheGem Theme Elements to version 5.12.1.1 or the latest available version from CodexThemes
  5. 5. Verify the update was successfully applied by checking the version number in the WordPress admin
  6. 6. Clear any caching mechanisms (site cache, CDN cache, browser cache)
  7. 7. Test the site functionality to ensure the update did not break existing features

Generated from the published advisory — verify against the referenced sources before acting.

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-42410 — 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-42410 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