Security and the software BarcodeMan runs
Which parts of BarcodeMan use PHP, whether the October 2026 PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 affect your store, and what to ask your host if you use WooCommerce.
On this page
If you use BarcodeMan on Shopify, Wix, or BigCommerce, the PHP vulnerabilities fixed on 21 October 2026 (CVE-2026-109618 and CVE-2026-109619) do not affect BarcodeMan, and you have nothing to do. If you use BarcodeMan for WooCommerce, the plugin runs on your host’s PHP, so make sure your host updates PHP. Updating the plugin cannot fix the PHP engine.
This page covers the software we build and deploy for BarcodeMan and Gookit Label API. It does not cover Shopify, Wix, BigCommerce, your web host, or other apps you use.
What BarcodeMan runs on
Every service we build and deploy for BarcodeMan runs on Node.js, and none of them includes PHP. Our API, which also serves Gookit Label API, runs on Node.js, and so does the service that renders label PDFs. The BarcodeMan app you open in Shopify, Wix, BigCommerce, or the WooCommerce workspace is a set of static files that runs in your browser.
| Where you use BarcodeMan | What runs BarcodeMan | PHP in the services we deploy |
|---|---|---|
| Shopify | Browser app, Node.js API | None |
| Shopify, earlier app version (v2) | Node.js server | None |
| Wix | Browser app, Node.js API | None |
| BigCommerce | Browser app, Node.js API | None |
| WooCommerce | Plugin on your WordPress site, browser workspace, Node.js API | None. The plugin runs on your host’s PHP. |
| Gookit Label API | Node.js API | None |
Does BarcodeMan use PHP?
Only in the WooCommerce plugin. BarcodeMan for WooCommerce, from WordPress.org or the Woo Marketplace, is PHP code that runs inside your WordPress site, on the PHP that your host provides. We do not operate that server. BarcodeMan on Shopify, Wix, and BigCommerce uses no PHP.
BarcodeMan reads your products, variations, and orders, plus customer names and addresses for address labels, through the WooCommerce REST API on your site. You approve that access on WooCommerce’s own screen. That REST API is part of WooCommerce on your site, so it also runs on your host’s PHP. For the full list of what the plugin sends and to whom, see WordPress external services.
Outside the plugin, we use PHP only in our automated tests. They run the plugin’s code to check it and do not receive store data.
Does BarcodeMan use Laravel?
No. None of the services we deploy includes PHP, so none uses Laravel. The WooCommerce plugin includes no Laravel or Composer packages. It loads only its own files and WordPress.
PHP security release of 21 October 2026 (CVE-2026-109618 and CVE-2026-109619)
What are CVE-2026-109618 and CVE-2026-109619?
They are two critical vulnerabilities in the PHP engine that can let an attacker run code on a server without logging in. The PHP project rates each one CVSS v4.0 9.2, critical. PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35 fix both. They were released on 21 October 2026.
According to php.net, the risk applies to PHP installations that serve web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed. The bug is in PHP itself, not in WordPress, WooCommerce, or a plugin.
Sources: the php.net security advisory, and the NVD entries for CVE-2026-109618 and CVE-2026-109619.
Is BarcodeMan affected by CVE-2026-109618 or CVE-2026-109619?
The services we deploy are not affected, because none of them includes PHP. On WooCommerce, the plugin runs on your host’s PHP, so your site’s exposure depends on the PHP build your host runs.
Are BarcodeMan’s servers patched to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35?
The question does not apply to the services we deploy. They include no PHP, so there is no PHP for us to update and no update timeline.
Do I need to do anything if I use BarcodeMan on Shopify, Wix, or BigCommerce?
No. You have nothing to install or change for BarcodeMan. If you use other apps, ask each app’s developer whether their servers run PHP.
Do I need to do anything if I use BarcodeMan for WooCommerce?
Yes. Make sure your site runs a PHP build that includes the 21 October 2026 fix.
- Check your PHP version. The next section shows where to find it.
- Compare it with the fixed release for its branch: 8.5.12, 8.4.27, 8.3.36, or 8.2.35.
- If your version is lower, ask your host whether their build includes the fix. A lower number can still be fixed, as the section on older version numbers explains.
- If the build is not fixed, ask your host to update PHP.
How do I check my PHP version in WordPress or WooCommerce?
Either of these screens shows the PHP version:
- In WordPress, go to Tools > Site Health, open the Info tab, and expand Server.
- In WooCommerce, go to WooCommerce > Status. The PHP version row is under Server Environment.
My host shows PHP 8.3.6 or another older number. Am I still vulnerable?
Not necessarily. Some Linux distributions fix PHP by adding the patch to their own package and keeping the original version number. For example, Ubuntu 24.04’s fixed package is 8.3.6-0ubuntu0.24.04.13, which keeps the version number 8.3.6. The version number alone cannot tell you whether your site is protected. Ask your host whether your PHP build includes the fix for CVE-2026-109618 and CVE-2026-109619.
What if my site runs PHP 7.4, 8.0, or 8.1?
The PHP project does not release updates for PHP 8.1 and older, so these versions have no official fixed release. php.net published source-code fixes for 7.4, 8.0, and 8.1 for people who build PHP themselves or whose vendor ships no fix. Some Linux distributions and support vendors also ship their own fixed builds. Ask your host whether your build includes the fix. If it does not, ask your host to move your site to a supported PHP version.
PHP 8.2 receives security fixes until 31 December 2026. See PHP supported versions for the dates of the other versions.
Where can I report a security issue to Gookit?
Email hi@gookit.co. Say which product and platform you use, and include the steps or URL that show the issue.
Questions about this article? Email our team.
Send feedback