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

CVE-2026-54189

HIGH · 7.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Unauthenticated Cross Site Scripting (XSS) in JetEngine <= 3.8.10 versions.

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

An unauthenticated Cross Site Scripting (XSS) vulnerability exists in JetEngine plugin for WordPress versions 3.8.10 and below. The vulnerability can be exploited without any authentication, allowing attackers to inject malicious scripts into web pages viewed by users.

MitigationUpdate JetEngine plugin to a version newer than 3.8.10. If a patch is unavailable, consider temporarily disabling the plugin or implementing Web Application Firewall (WAF) rules to block XSS attack patterns.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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. Check JetEngine plugin version via WordPress admin
    Navigate to Plugins > Installed Plugins in the WordPress admin dashboard. Locate 'JetEngine' in the list and read the version number displayed beneath the plugin name.
    Affected if The displayed version is 3.8.10 or lower.
  2. Check JetEngine plugin version via filesystem
    Access the WordPress installation via FTP or file manager. Navigate to /wp-content/plugins/jetengine/ and open the main plugin file (usually jetengine.php or readme.txt). Look for the 'Version:' field in the file header.
    Affected if The version number found is 3.8.10 or lower.
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that JetEngine shows as 'Active' rather than 'Inactive' or 'Must Use'.
    Affected if JetEngine is active and the version is 3.8.10 or lower.
  4. Review version in wp_options database table
    Access the WordPress database via phpMyAdmin or CLI. Query: SELECT option_value FROM wp_options WHERE option_name = 'jet_engine_version' LIMIT 1; (note: the option name may vary; also check 'jetengine_version' or similar).
    Affected if The stored version value is 3.8.10 or lower.

A WordPress site running JetEngine version 3.8.10 or below with the plugin active is vulnerable to unauthenticated XSS attacks and is affected by CVE-2026-54189.

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 JetEngine plugin to a version newer than 3.8.10. If a patch is unavailable, consider temporarily disabling the plugin or implementing Web Application Firewall (WAF) rules to block XSS attack patterns.

Recommended fix Moderate confidence

JetEngine version > 3.8.10 (latest stable release)

  1. 1. Verify current JetEngine version installed on the WordPress site
  2. 2. Create a complete backup of the WordPress site (database and files)
  3. 3. Update JetEngine plugin to the latest available version (newer than 3.8.10)
  4. 4. Clear any caching mechanisms after the update
  5. 5. Verify the update was successful and the plugin functions correctly
Caveat Review JetEngine changelog for any breaking changes between 3.8.10 and the target upgrade version

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
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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