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

Back
New CVE Detected

CVE-2026-76599 – Unauthenticated Database Table & Prefix Disclosure – 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-76599 is an unauthenticated information disclosure vulnerability in the Fabrik extension for Joomla, allowing unauthenticated attackers to enumerate arbitrary database table names, table prefixes, and column structures. It affects all Fabrik releases from 1.0.0 through 4.7.1 and carries a HIGH severity rating (CVSS 8.7). The flaw was fixed in Fabrik 4.7.2.

Technical details

  • Root cause: the ajax_tables method in Fabrik’s elements model fails to enforce authentication or authorization checks before returning database schema information.
  • Trigger conditions: an attacker sends a request to the exposed AJAX endpoint on a site running a vulnerable Fabrik version; no login or session is required.
  • Attack vector: network-based, remotely exploitable over HTTP with no privileges and no user interaction (AV:N/AC:L/AT:N/PR:N/UI:N).
  • Impact: disclosure of arbitrary database table names, table prefixes, and column names, which can expose sensitive site/database architecture and aid follow-on attacks (e.g., SQL injection targeting). The vulnerability is scoped to confidentiality impact only; integrity and availability are not affected.

Affected software

  • Fabrik extension for Joomla, versions 1.0.0 through 4.7.1 (all releases prior to the fix).

Severity

  • CVSS 4.0 Base Score: 8.7 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Fabrik to version 4.7.2 or later, where the ajax_tables access control issue has been fixed.
  • If immediate patching is not possible: restrict or disable public access to the Fabrik AJAX/component endpoints (e.g., via web server or WAF rules blocking unauthenticated requests to com_fabrik AJAX handlers) until the upgrade can be applied, and review database/table naming for exposure risk.

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