Skip to content
Web

CVE-2026-2395

9.8
Critical
EPSS 0.47%Jul 23, 2026

SQL injection in Xpoda No Code Platform allows arbitrary database queries.

common questions

Is CVE-2026-2395 being exploited?

Not confirmed. CVE-2026-2395 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.47% probability of exploitation in the next 30 days.

How severe is CVE-2026-2395?

CVE-2026-2395 is rated Critical with a CVSS score of 9.8. 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-2395?

Not known from our data. No patch reference has been recorded for CVE-2026-2395, 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-2395 affect?

CVE-2026-2395 affects Xpoda No Code Platform v4.3.1.0 through 20260722. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-2395?

Block external access, apply WAF rules, enforce input validation, and install vendor patch when released.

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

executive summary
technical analysis
affected
Xpoda No Code Platform v4.3.1.0 through 20260722
impact

Remote SQL injection: attackers can read, modify, exfiltrate or destroy database records and potentially bypass authentication.

action required

Immediate action required

affected versions
Xpoda Türkiye Informatics Technology Inc. No Code Platform
  • affected>= 4.1.3 and < 4.1.4

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