CVE-2026-49084
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 · uneditedUnauthenticated SQL Injection 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 · high confidenceAn unauthenticated SQL injection vulnerability exists in JetEngine plugin versions prior to 3.8.9.1, allowing remote attackers to execute arbitrary SQL queries via unauthenticated HTTP requests due to improper input sanitization in database queries.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify JetEngine plugin installation and versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins, locate JetEngine, and note the version number displayedAffected if JetEngine version is present and is lower than 3.8.9.1
-
Confirm plugin file existence via filesystemAccess the WordPress wp-content/plugins directory and locate the jetengine folder; check the main plugin file (jetengine.php) or readme.txt for the version numberAffected if Version listed in plugin files is below 3.8.9.1
-
Verify plugin is active and accessibleIn WordPress admin > Plugins, confirm JetEngine is activated; check if the site is exposing JetEngine endpoints to unauthenticated users by reviewing published JetEngine widgets or dynamic contentAffected if Plugin is active and its functionality is publicly accessible without authentication
-
Inspect HTTP access logs for suspicious query patternsReview web server access logs for requests to JetEngine-related endpoints containing SQL operators (UNION, SELECT, INSERT, UPDATE, DELETE) or unusual URL parameters that may indicate exploitation attemptsAffected if Log entries show SQL injection patterns targeting JetEngine endpoints
A system is affected if JetEngine plugin version is below 3.8.9.1 and the plugin is active and exposed to unauthenticated HTTP requests
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade JetEngine to version 3.8.9.1 or later to remediate the vulnerability; if immediate patching is not feasible, implement web application firewall rules or temporarily restrict access to the affected plugin endpoints.
JetEngine 3.8.9.1 or later
- Update JetEngine plugin to version 3.8.9.1 or later through the WordPress plugin repository or your site's plugin management interface
- Verify the update was successful by checking the plugins list in WordPress admin
- Review site logs for any signs of exploitation attempts targeting the SQL injection vulnerability
- Consider running a security scan to ensure no compromise occurred prior to patching
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49084 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49084 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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