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

Back
New CVE Detected

CVE-2026-76607 – Improper Access Control / Unauthorized File Access – Fabrik Joomla Extension (1.0.0

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-76607 is a missing access-control-list (ACL) check in the download element of the Fabrik extension for Joomla, allowing unauthorized access to files served through that element. The flaw affects all Fabrik releases from 1.0.0 through 4.7.3 and has been assigned a CVSS v4.0 base score of 10.0 (Critical) by the Joomla CNA. The issue was reported by Phil Taylor of mySites.guru.

Technical details

  • Root cause: The Fabrik download element does not perform the expected ACL/permission check before serving a file, per CWE-284 (Improper Access Control).
  • Trigger conditions: A request to the download element’s file-serving functionality on a site running an affected Fabrik version.
  • Attack vector: Network-based; the published vector string indicates no privileges and no user interaction are required (PR:N/UI:N).
  • Impact: High impact to confidentiality, integrity, and availability, with the CVSS v4.0 vector also reflecting high subsequent-system impact (SC:H/SI:H/SA:H), consistent with unauthorized retrieval of files that should be access-restricted.

Affected software

  • Fabrik extension for Joomla (fabrikar.com), versions 1.0.0 through 4.7.3
  • Versions 4.7.3 and later are not affected per the CVE record

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

Mitigation and recommended actions

  • Immediate: Upgrade Fabrik to a version later than 4.7.3 (the version at which the CVE record marks the product as unaffected). Obtain the update directly from fabrikar.com.
  • If unable to patch immediately: Restrict or disable access to the Fabrik download element’s front-end endpoint until the upgrade can be applied, and audit logs for unexpected file-download requests.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /media/com_fabrik/, /components/com_fabrik/

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge