dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-28134

HIGH · 8.5 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Control of Generation of Code ('Code Injection') vulnerability in Crocoblock JetEngine jet-engine allows Remote Code Inclusion.This issue affects JetEngine: from n/a through <= 3.7.2.

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

JetEngine plugin for WordPress contains a code injection vulnerability allowing remote code inclusion. The vulnerability stems from improper control of code generation, likely due to insufficient input validation on user-supplied data. This could allow attackers to include and execute malicious code on the affected WordPress installation.

MitigationUpdate JetEngine to the latest version immediately. If an update is unavailable, disable the plugin until a patch is released. Review recent access logs for suspicious activity and consider a security audit of the WordPress installation.

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

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 JetEngine plugin installation
    Check if the JetEngine plugin exists in your WordPress installation. Common paths include /wp-content/plugins/jetengine/ or access it via Plugins > Installed Plugins in the WordPress admin dashboard.
    Affected if JetEngine plugin is present in the WordPress installation
  2. Identify installed JetEngine version
    Locate the version number in the plugin header. In the WordPress admin, go to Plugins > Installed Plugins > JetEngine and view the version number. Alternatively, check the main plugin file (jetengine.php) for the 'Version' comment header.
    Affected if Unable to determine the version or version is earlier than the patched release
  3. Compare version to known affected ranges
    Document the installed version number and compare it against any official JetEngine security advisories or release notes mentioning CVE-2026-28134. If no specific ranges are publicly documented, note that all versions prior to the latest release may be considered at risk.
    Affected if Installed version falls within an affected range (if known) or is older than the patched version
  4. Check for suspicious files in plugin directory
    Inspect the /wp-content/plugins/jetengine/ directory for any unexpected PHP files, particularly in subdirectories like /includes/ or /modules/. Look for files with randomized names, recent modification dates, or files containing eval(), base64_decode(), or shell_exec() calls.
    Affected if Unexpected or malicious PHP files are present in the plugin directory
  5. Review WordPress access logs for code inclusion attempts
    Examine server access logs (typically in /wp-content/ or server logs directory) for requests to JetEngine-related endpoints that may indicate exploitation attempts, such as unusual query parameters or POST data targeting dynamic code generation features.
    Affected if Logs show suspicious requests targeting JetEngine functionality

A user is affected if JetEngine is installed with a version prior to the patched release and the vulnerable code generation feature is accessible to attackers.

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 immediately. If an update is unavailable, disable the plugin until a patch is released. Review recent access logs for suspicious activity and consider a security audit of the WordPress installation.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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