Skip to content
Web

CVE-2026-65766

9.2
Critical
EPSS 0.24%Patch availableJul 27, 2026

Unauthenticated SQL injection in SP Page Builder <6.7.1 allowing database compromise.

common questions

Is CVE-2026-65766 being exploited?

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

How severe is CVE-2026-65766?

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

Yes. A fix has been recorded for CVE-2026-65766. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-65766 affect?

CVE-2026-65766 affects JoomShaper SP Page Builder <6.7.1 (Joomla extension), Joomla sites using SP Page Builder. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-65766?

Update SP Page Builder to >=6.7.1; if not possible, disable the extension and review DB access/logs.

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

executive summary
technical analysis
affected
JoomShaper SP Page Builder <6.7.1 (Joomla extension)Joomla sites using SP Page Builder
impact

Unauthenticated SQL injection via Dynamic Content 'order' parameter; attackers can read/modify DB, exfiltrate data, and enable account takeover.

action required

Immediate action required

affected versions
joomshaper.com SP Page Builder extension for Joomla
  • affected1.0.0-6.7.0

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