Download websites that use FooPlugins FooGallery

About FooPlugins FooGallery

A WordPress site is a pile of decisions, most of them made once and then left alone for years. A gallery plugin is a good example. Somebody needed images arranged in a grid, installed FooGallery, configured it in an afternoon, and the plugin has been rendering the same pages ever since with nobody thinking about it again.

The kind of site that reaches for a dedicated gallery is reasonably predictable. Photographers, studios, venues, museums, property listings, schools and product catalogues all need images presented in bulk with some control over layout, and the Photo galleries platform underneath does not do it well enough on its own. Presence of the plugin therefore hints at visual content as a core part of the site's purpose, which is a useful filter for anyone selling image hosting, print services, media licensing or performance optimisation, since image heavy pages are also the slow ones.

The economics behind the plugin shape the population too. FooPlugins publishes a free edition under GPL v2 alongside a paid tier that adds filtering, video and commerce integrations, so the sites we detect mix hobby installs with paying customers and the two look broadly similar from outside. The plugin is written in PHP and runs on the site's own server, which means the site owner, not the vendor, decides when and whether it is ever updated. Available since 2014, it has been installed across enough successive WordPress eras that the deployed base spans a wide stretch of the platform's history.

Version data makes that concrete. We record 106 distinct versions across the sites we scan, with 3.3.3 appearing more than any other. A spread that wide on a self hosted plugin is normal and consequential. Premium builds update through a licence key that lapses when a subscription is not renewed, free installs update only when somebody logs into the dashboard, and a site left to run unattended keeps whatever build it had. For security research the practical question is never how many sites run the plugin but how many run a release covered by a given advisory, and only version level data answers it.

Detection has a blind spot worth stating, and it runs in one direction. A gallery plugin announces itself in the markup and asset paths of pages that actually render a gallery, so a site using it deep in a portfolio section while serving a plain home page can pass unnoticed, and caching or optimisation plugins that concatenate and rewrite assets can erase the fingerprint entirely. As of October 2026 we see it on 5,162 sites, and the real installed base is larger than that. A per domain lookup confirms one site and settles nothing else. The extract is what lets an agency size a migration market, a competing plugin vendor find displacement targets, or a researcher measure how long an outdated release survives in the wild.