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

New CVE Detected

CVE-2026-65880 – Unauthenticated RCE via Signature Field – Balbooa Forms for Joomla (all versions…

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

Summary

CVE-2026-65880 is a critical unauthenticated remote code execution vulnerability in Balbooa Forms, a form-builder extension for the Joomla CMS developed by balbooa.com. The flaw resides in insecure form processing logic that is triggered when a form includes the signature field type, enabling a fully unauthenticated remote attacker to execute arbitrary code on the underlying server. The vulnerability carries a maximum CVSS 4.0 score of 10.0, with no complexity, no required privileges, no user interaction, and full impact on confidentiality, integrity, and availability of both the affected system and its surrounding environment.

Technical details

  • Root cause: Insecure form processing logic (CWE-94: Improper Control of Generation of Code / Code Injection) that is triggered when a submitted form contains the signature field type.
  • Trigger conditions: Any publicly accessible Joomla form that includes a signature field can be exploited by submitting a crafted request — no user account, login session, or prior knowledge of site internals is required.
  • Attack vector: Fully remote and unauthenticated. The Balbooa Forms component is registered as com_baforms within Joomla and renders on public-facing pages, making it directly reachable by any network attacker.
  • Impact: Successful exploitation results in remote code execution on the host server, enabling full system compromise including data exfiltration, web shell deployment, and lateral movement within the hosting environment.

Affected software

  • Balbooa Forms for Joomla — all versions from 1.0.0 through 2.4.2.1 (all versions prior to 2.4.3)

Note for organizations that previously patched CVE-2026-56291: That earlier Balbooa Forms vulnerability was addressed in version 2.4.1 (released July 9, 2026). Versions 2.4.1 and 2.4.2 remain fully exposed to CVE-2026-65880. Upgrading to 2.4.3 is required.

Severity

CVSS 4.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

A CVSS v3.1 score has not been published in the official CVE record; the CVSS 4.0 score above is the authoritative severity rating for this vulnerability.

Mitigation and recommended actions

  • Immediate action: Upgrade Balbooa Forms to version 2.4.3 or later. This is required for all deployments, including those already running 2.4.1 or 2.4.2.
  • If immediate patching is not possible:
    • Temporarily disable forms that use the signature field type until the upgrade can be applied.
    • Apply web application firewall (WAF) rules to restrict or monitor requests to the com_baforms component endpoint from untrusted external sources.
    • Restrict public access to affected form pages at the network or application layer as an interim control.

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