dbcve.org
JetelementsWordPress extension · Crocoblock

CVE-2025-0371

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-21
Fix available
A fix is available. Upgrade to 2.7.3 or later.
See remediation →
58/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
The JetElements plugin for WordPress is vulnerable to Stored Cross-Site Scripting via several widgets in all versions up to, and including, 2.7.2.1 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 JetElements WordPress plugin fails to properly sanitize user-supplied attributes in multiple widgets and escape them on output, allowing authenticated contributors+ to inject persistent JavaScript payloads. These scripts execute in victim browsers whenever the injected pages are accessed.

MitigationUpdate JetElements to the latest version and audit existing pages for malicious widget configurations. Enforce least-privilege on contributor-level accounts until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JetelementsWordPress extension
Affected:< 2.7.3

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 JetElements plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate the JetElements by Crocoblock plugin. Note the installed version number displayed.
    Affected if JetElements is installed and the version listed is below 2.7.3 (for example, 2.7.2, 2.7.1, or earlier)
  2. Confirm the exact version number
    Check the plugins list for the version column, or if you have file system access, inspect the plugin main file header in /wp-content/plugins/jet-elements/ to read the Version field.
    Affected if The Version field reads less than 2.7.3
  3. Identify user accounts with contributor-level access or higher
    In WordPress admin, go to Users and review the role column. Look for any accounts assigned the Contributor, Author, Editor, or Administrator roles.
    Affected if There exists at least one user account with Contributor, Author, Editor, or Administrator role (since these roles can access the widget editor)
  4. Inspect pages containing JetElements widgets for injected scripts
    Edit a page or post that contains JetElements widgets. In Elementor or the classic editor, review widget settings for any attribute fields (such as custom CSS classes, headings, or link URLs) that contain unusual characters or appear Base64-encoded. Alternatively, export page content as XML and search the raw data for script tags, javascript:, or onload/onerror event handlers within JetElements widget shortcodes.
    Affected if Any JetElements widget settings contain raw script tags, javascript: URIs, or HTML event handler attributes (onclick, onload, onerror, etc.) that were not intentionally added by an administrator

You are affected if JetElements is installed at a version below 2.7.3 AND at least one contributor-level or higher user account exists in the WordPress site.

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
Upgrade available Upgrade to 2.7.3 or later
Fixed in 2.7.3
Interim mitigation

Update JetElements to the latest version and audit existing pages for malicious widget configurations. Enforce least-privilege on contributor-level accounts until patched.

Recommended fix High confidence

JetElements version 2.7.3 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find JetElements in the plugin list
  4. Check if an update is available (version 2.7.3 or later)
  5. If update available, click 'Update Now' to update to the latest version
  6. If no automatic update, manually download JetElements version 2.7.3 or later from crocoblock.com
  7. Deactivate the current JetElements plugin
  8. Delete the existing JetElements plugin

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

Fix this in Jetelements 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 the upgrade done

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-2025-0371 — 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-2025-0371 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