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

CVE-2026-49074

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.9.1 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

Unauthenticated Cross Site Scripting (XSS) vulnerability in JetEngine plugin for WordPress versions 3.8.9.1 and below. The vulnerability can be exploited without requiring authentication, allowing attackers to inject malicious scripts into web pages viewed by other users.

MitigationUpdate JetEngine to the latest version beyond 3.8.9.1 which contains the patched version. Until patched, consider restricting access to the affected endpoints or implementing additional input validation at the web application firewall level.

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. Confirm JetEngine plugin is installed
    Navigate to WordPress admin > Plugins and look for JetEngine in the installed plugins list, or check the /wp-content/plugins/jet-engine directory exists on the server
    Affected if JetEngine plugin is present in the WordPress installation
  2. Check installed JetEngine version
    In WordPress admin, go to Plugins > JetEngine > View Details, or inspect the main plugin file header for the Version field, or use WP-CLI: wp plugin get jet-engine --field=version
    Affected if The reported version is 3.8.9.1 or lower
  3. Verify the plugin is active
    Check the Plugins page in WordPress admin to confirm JetEngine status shows as 'Active', or query the database wp_options table for option_name='active_plugins' containing jet-engine
    Affected if JetEngine is activated and running on the site
  4. Confirm unauthenticated access is possible
    Attempt to access the suspected vulnerable endpoint without logging in (e.g., any public-facing JetEngine widget or shortcode), or verify that WordPress general settings do not restrict site access to logged-in users only
    Affected if The site allows unauthenticated visitors and JetEngine components are publicly accessible

The environment is affected if JetEngine plugin is installed, active, and running version 3.8.9.1 or below with unauthenticated access to the site enabled.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update JetEngine to the latest version beyond 3.8.9.1 which contains the patched version. Until patched, consider restricting access to the affected endpoints or implementing additional input validation at the web application firewall level.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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