Security Response, Financial Impact on Agencies, and Urgent Request for Joomla 3 Security Patches

Dear Balbooa Team,

As a long-term agency customer managing numerous client websites, recent security incidents and Balbooa’s official forum response force me to address a critical issue regarding software accountability and client trust.

The technical vulnerabilities themselves are severe, but the response on this forum has turned a software flaw into an operational and financial crisis for your agency client base:

Unbillable Agency Costs: Agencies have spent dozens of unbillable hours per site cleaning up compromises, auditing code, and reassuring anxious clients. This has resulted in significant financial and operational costs for agencies following vulnerabilities in commercial software.

Inadequate Workarounds: Advising paying customers to "apply .htaccess rules" or deferring responsibility to hosting providers is unacceptable. While hosting providers can implement mitigating measures, they cannot correct vulnerabilities in the application's source code. Addressing those vulnerabilities is ultimately the responsibility of the software vendor.

The Reality of Joomla 3: Many production sites remain on Joomla 3 due to client budget cycles or complex custom integrations. Denying security patches under the statement of "only supporting current Joomla versions" ignores the real-world environment of the agencies that helped build your user base. We are not asking for new features, we are asking for basic code safety on existing installations.

Trust is built on accountability. We have already cancelled our subscriptions for BA Forms and BA Gallery due to a complete loss of confidence in their security integrity. We currently remain on Gridbox solely due to the technical weight of migrating off a core page builder, not because trust remains intact.

We formally request Balbooa to take the following steps:

Release critical security-only patches for the Joomla 3 versions of Gridbox, BA Forms, and BA Gallery.

Take clear ownership of application-level vulnerabilities instead of redirecting users to host-level workarounds or community suggestions.

Establish rigorous, professional security testing as a fundamental standard prior to releasing feature updates.

This is about the long-term viability of the agencies that have promoted your software for years. I urge you to take ownership of this situation and provide your user base with the security commitment they paid for.

Sincerely,
Elmer

Replies are visible only to logged in members with an active subscription.