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

New CVE Detected

CVE-2026-76605 – Unauthenticated Remote Code Execution – Fabrik Joomla Extension 1.0.0 through 4.7.3

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

Summary

CVE-2026-76605 is a critical remote code execution vulnerability in the Fabrik extension for Joomla (fabrikar.com), caused by improper control of code generation (CWE-94) in the extension’s image element component. The flaw affects every released version of Fabrik from 1.0.0 through 4.7.3 and carries a maximum CVSS v4.0 base score of 10.0 (Critical), as it requires no authentication and no user interaction to exploit over the network.

Technical details

  • Root cause: Improper control of generation of code (CWE-94 – code injection) within Fabrik’s image element component.
  • Trigger conditions: The vulnerable code path is reachable through the image element functionality shipped with com_fabrik on any Joomla site running an affected Fabrik version.
  • Attack vector: Network-based (AV:N), with low attack complexity, no attack requirements, no privileges required, and no user interaction (per the published CVSS v4.0 vector).
  • Impact: High confidentiality, integrity, and availability impact at both the vulnerable-system and subsequent-system level, consistent with full remote code execution on the affected web server.

Affected software

  • Fabrik extension for Joomla, versions 1.0.0 through 4.7.3 (all releases up to and including 4.7.3).

Severity

  • CVSS v4.0 Base Score: 10.0 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
  • CWE-94: Improper Control of Generation of Code (‘Code Injection’)

Mitigation and recommended actions

  • Immediate: Upgrade Fabrik to a release newer than 4.7.3. At the time of publication, the vendor (fabrikar.com) had not published a detailed advisory naming the specific fixed version — administrators should check the official Fabrik downloads/changelog and apply the latest available release.
  • If no patch can be applied immediately: Restrict or disable public access to the Fabrik image element functionality (e.g., via web server or WAF rules blocking the relevant com_fabrik front-end endpoints) until the update is applied, and monitor web server logs for anomalous requests targeting com_fabrik.

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