Skip to content
Web

CVE-2026-73365

CRITICAL
Critical
EPSS 0.38%Aug 19, 2026

Unauthenticated SQL injection in JetAppointment <=2.5.2 allows database compromise.

common questions

Is CVE-2026-73365 being exploited?

Not confirmed. CVE-2026-73365 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.

How severe is CVE-2026-73365?

CVE-2026-73365 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-73365?

Not known from our data. No patch reference has been recorded for CVE-2026-73365, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-73365 affect?

CVE-2026-73365 affects JetAppointment <=2.5.2, WordPress sites using JetAppointment. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73365?

Disable or remove the plugin until vendor patch; apply vendor fix immediately when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
JetAppointment <=2.5.2WordPress sites using JetAppointment
impact

Unauthenticated SQL injection enabling attackers to read/modify database records, steal credentials, alter bookings, and potentially escalate access.

action required

Immediate action required

affected versions
Crocoblock. Jetimpex Inc. JetAppointment
  • affected<= 2.5.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free