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

New CVE Detected

CVE-2026-65876 – Unauthenticated SQL Injection – SP Page Builder for Joomla (< 6.7.1)

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

Summary

CVE-2026-65876 is a critical, unauthenticated SQL injection vulnerability in SP Page Builder, a widely-deployed page-builder extension for Joomla developed by joomshaper.com. The flaw arises from improper validation of the catid parameter in the public-facing loadMoreArticles endpoint, allowing any anonymous attacker over the network to inject arbitrary SQL commands. The vulnerability carries a CVSS 4.0 score of 9.2 (Critical) and affects all SP Page Builder versions from 1.0.0 through 6.7.0.

Technical details

  • Root cause: Improper neutralization of user-supplied input (CWE-89) in the catid parameter handled by the loadMoreArticles HTTP endpoint. The endpoint performs no adequate validation or sanitization before incorporating the parameter into SQL queries.
  • Trigger conditions: No authentication or user interaction is required. An attacker sends a crafted HTTP request to the loadMoreArticles endpoint with a malicious catid value. This endpoint is publicly reachable on any Joomla site running the extension.
  • Attack vector: Network (AV:N); no prior access, credentials, or victim interaction needed (PR:N, UI:N). Attack complexity is Low (AC:L) with no attack requirements (AT:N).
  • Impact: High confidentiality impact at both the vulnerable component and subsequent system levels (VC:H, SC:H). Successful exploitation enables an unauthenticated attacker to extract data from the Joomla database, including user credentials, session tokens, configuration data, and any other information stored within the database. No integrity or availability impact is asserted in the CVSS vector.
  • Credited researcher: Krzysztof Zając, CERT PL.

Affected software

  • SP Page Builder extension for Joomla by joomshaper.com — versions 1.0.0 through 6.7.0 (all versions prior to 6.7.1)

Severity

  • CVSS 4.0 Base Score: 9.2 (Critical)
  • CVSS 4.0 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

Mitigation and recommended actions

  • Immediate action — patch now: Upgrade SP Page Builder to version 6.7.1 or later, which contains the vendor-issued fix for this vulnerability. This is the only confirmed remediation.
  • If immediate patching is not possible: Restrict or block public access to the loadMoreArticles endpoint at the web application firewall or reverse proxy layer, and monitor for anomalous SQL-pattern traffic directed at Joomla instances running SP Page Builder.
  • Audit exposure: Review all Joomla deployments within your environment for the presence of the SP Page Builder extension and prioritize upgrading across all instances.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. SP Page Builder has been an active target throughout 2026, and this new unauthenticated SQL injection vector in the same product raises the urgency for organizations with exposed Joomla deployments. 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