What’s New in FireBox: May & June 2026

Over the past two months, we focused less on new headline features and more on the things that keep FireBox reliable: security, compatibility, and a smoother editing experience.

Across the 3.1.7 and 3.1.8 releases, we hardened protection for form submission exports, continued refining WordPress 7.0 compatibility, improved responsive design controls, and fixed a handful of issues reported in real-world use.

Follow us

If you missed our earlier updates, you can catch up with the March & April 2026 and January & February 2026 releases.

Stronger Security for Form Submission Exports

The most important change in this cycle is a security fix.

We closed a gap that could allow unauthenticated access to the form submissions CSV export endpoint. Exporting your submissions now requires the proper permissions, so the lead data your campaigns collect stays protected and can only be downloaded by authorized users.

If you collect leads or contact form entries through FireBox, we recommend updating to version 3.1.8 to ensure your data is covered.

Continued WordPress 7.0 Compatibility

We continued improving FireBox compatibility with WordPress 7.0.

Following the initial compatibility work in our previous release, this update resolves additional inconsistencies so your campaigns continue to behave as expected on the latest version of WordPress.

Improved Responsive Design Controls

We also refined the styling in the responsive controls inside the campaign editor.

These controls are what let you adjust how a campaign looks across Desktop, Tablet, and Mobile. The cleaner styling makes them easier to read and use, so switching between devices and fine-tuning each layout feels more predictable.

Improvements and Fixes

This update also includes several improvements and fixes based on real usage:

• Campaign Editor Stability: Fixed an issue where changing block settings in the campaign editor could unexpectedly switch back to the FireBox panel.
• Accurate Google Analytics Tracking: Google Analytics no longer triggers extra page views when tracking popup events, so your campaign data and your overall site analytics stay accurate.
• PHP 8.4 Compatibility: Fixed a PHP deprecation notice for fputcsv() during the form submissions CSV export on PHP 8.4 and later.

Conclusion

May and June focused on strengthening the foundation: protecting your submission data, staying compatible with the latest WordPress, and smoothing the editing experience.

With a key security fix shipped, WordPress 7.0 compatibility improved, and a few practical bugs resolved, FireBox remains dependable as the platform around it continues to evolve.

As always, thank you for your feedback, bug reports, and suggestions. They continue to shape how FireBox evolves.