Skip to content
Web

CVE-2026-12076

9.3
Critical
EPSS 0.53%Jun 30, 2026

SQL injection in Raytha CMS OData filters allows remote DB compromise.

common questions

Is CVE-2026-12076 being exploited?

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

How severe is CVE-2026-12076?

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

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

CVE-2026-12076 affects Raytha CMS v1.5.2 (and possibly other versions), PostgreSQL backend used by Raytha. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-12076?

Patch when available; restrict OData access; validate inputs; enable WAF.

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

executive summary
technical analysis
affected
Raytha CMS v1.5.2 (and possibly other versions)PostgreSQL backend used by Raytha
impact

Remote unauthenticated SQLi via OData enables full PostgreSQL DB compromise and credential access.

action required

Immediate action required

affected versions
Raytha Raytha
  • affected1.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