Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-65766 – Unauthenticated SQL Injection – SP Page Builder for Joomla < 6.7.1

Be the first to know when new zero-days emerge:

Summary

CVE-2026-65766 is a critical unauthenticated SQL injection vulnerability in SP Page Builder, a widely deployed page-building extension for Joomla developed by JoomShaper. The flaw exists in the Dynamic Content endpoint, where the direction order parameter is concatenated directly into a SQL ORDER BY clause without validation, enabling any unauthenticated remote attacker to extract the full contents of the Joomla database. This vulnerability was published on July 27, 2026 and carries a CVSS 4.0 score of 9.2 (Critical).

Technical details

  • Root cause: The direction parameter accepted by the Dynamic Content endpoint (in dynamic_content.php and CollectionData.php) is inserted raw into the ORDER BY clause of a database query without sanitization or allowlist validation. As ORDER BY direction values cannot be safely parameterized in SQL, the only safe mitigation is strict value restriction to ASC or DESC — which was absent in all versions prior to 6.7.1.
  • Authentication bypass: Although the endpoint requires a Joomla CSRF token, Joomla issues valid tokens to every visitor including unauthenticated users, rendering this check ineffective as an access control.
  • Trigger conditions: An attacker needs only to craft an HTTP request to the Dynamic Content endpoint with a malicious direction value. No credentials, session, or user interaction are required.
  • Attack vector: Network-accessible; exploitable remotely over the internet against any exposed Joomla site running the affected extension.
  • Impact: Full database read access — including user account records, password hashes, session tokens, the Joomla site secret, and all stored content. Exploitation was demonstrated via time-based blind SQL injection.

Affected software

  • SP Page Builder extension for Joomla, versions 1.0.0 through 6.7.0 (all versions prior to 6.7.1)

Severity

  • CVSS 4.0 Base Score: 9.2 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
  • Both direct system confidentiality (VC:H) and subsequent system confidentiality (SC:H) are rated HIGH, reflecting the ability to exfiltrate the entire Joomla database including credentials, session tokens, and all stored records held in the underlying system.

Mitigation and recommended actions

  • Immediate: Update SP Page Builder to version 6.7.1 or later. The fix restricts the direction parameter to only the values ASC or DESC before query execution, and adds permission checks that prevent anonymous access to the Dynamic Content endpoint.
  • If patching is not immediately possible: Restrict public access to Dynamic Content endpoints via web application firewall rules or server-level controls blocking unauthenticated requests to the SP Page Builder component (com_sppagebuilder).

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge