Vulnerability report

Exploited in the wild High confidence Not in CISA KEV

CVE-2026-49076

WordPress JetEngine plugin <= 3.8.9.1 - SQL Injection vulnerability

Crocoblock / JetEngine · 0 to <= 3.8.9.1

View live feed Monitor via API Watch CVE-2026-49076
Severity
CVSS 9.3 · Critical
Confidence
High
Exploit status
Exploited in the wild
EPSS
0.4%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2026-49076 is an unauthenticated WordPress JetEngine plugin <= 3.8.9.1 - SQL Injection vulnerability. Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is high. Also confirmed by third-party sources.

Who is affected?

Crocoblock / JetEngine 0 to <= 3.8.9.1.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

WordPress JetEngine plugin <= 3.8.9.1 - SQL Injection vulnerability

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Crocoblock JetEngine jet-engine allows Blind SQL Injection.This issue affects JetEngine: from n/a through 3.8.9.1.

Crocoblock Affected
JetEngine jet-engine
Through 3.8.9.1
Published
17 Jun 2026
Exploitation Reported
28 Sep 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

wordpress

CVE References

  • CVE Record CVE.org · CVE Record https://www.cve.org/CVERecord?id=CVE-2026-49076
  • VDB Entry — patchstack.com patchstack.com · VDB Entry https://patchstack.com/database/wordpress/plugin/jet-engine/vulnerabi...

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

CVE

Recorded 28 Sep 2026

A trusted third party reported exploitation.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CVE First 2026-09-28 06:01 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

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

EPSS

0.4%

Weaknesses

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') CWE-89

Timeline

From disclosure to observed exploitation

  1. 06:01 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

  2. 09:51 UTC

    CVE published

    Vulnerability disclosed publicly

  3. 10:27 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

View Pro pricing Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2026-49076

Free JSON includes basic KEV fields 
{
  "cve_id": "CVE-2026-49076",
  "confidence": "High",
  "cvss_score": 9.3,
  "cvss_estimated": false,
  "epss_score": 0.004,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}