On October 28, 2026, Cloudways flagged one of the WooCommerce stores we manage with a high-severity warning: the Lumise Product Designer plugin, version 2.1.2 and below, has an unauthenticated arbitrary file read vulnerability. There was no update to install. The newest version on CodeCanyon was the one already running on the site.
If you run a print shop, apparel brand, or any store that lets customers design their own products, there is a good chance Lumise is on your site. Here is what the vulnerability means, and exactly what I changed to close it while we wait for an official fix.
What the Vulnerability Is
The issue is tracked as CVE-2026-15323, rated High (CVSS 7.5) by Patchstack. In plain terms, the plugin could be tricked into reading files from the server that it should never touch, and handing the contents back to whoever asked. No login was required.
The file attackers go after first is wp-config.php. It holds your database username and password plus the secret keys WordPress uses to sign logins. With those, someone can reach your customer and order data or forge an admin session.
While I was in the code, I also found a stored cross-site scripting (XSS) issue that is still present in 2.1.2. Patchstack reported an XSS in 2.1.1 earlier in October with no official patch. A visitor could submit a “bug report” from the designer, and the plugin displayed it in wp-admin without cleaning it, so a script hidden in that report would run when an admin opened the page.
I’m keeping the attack mechanics out of this post on purpose. There is no official patch yet, and plenty of stores are still exposed.
How I Fixed It: Every File I Changed
I patched five files in the plugin, tested the new checks against 15 attack-style inputs and the normal product images, and packaged it as version 2.1.2.1. Customer designs, carts and settings live outside the plugin, so they stay put.
| File | What I changed |
|---|---|
core/cart.php | The add-to-cart handler now only loads images that are genuine image files inside Lumise’s own upload folder or its built-in product images. Server paths, outside URLs, ../ tricks, PHP stream wrappers and symlinks are all rejected. Cart IDs are limited to letters, numbers, dashes and underscores. This is the main fix for CVE-2026-15323. |
core/includes/lib.php | Design screenshots are only saved if they decode to a real PNG, JPG, GIF or WEBP image, as a second layer of protection. The PDF download link now validates and escapes its ID before it goes anywhere near the database or a file path. |
core/includes/ajax.php | Visitor bug reports are stripped of HTML. The “report bug” action is now admin-only (it was open to anyone). Font names used to build PDFs can no longer contain folder paths. |
core/admin/pages/bugs.php | Bug report text is escaped before it is shown in the admin list. |
core/includes/views.php | Admin text boxes can no longer be broken out of by stored content, which closes the XSS on the bug edit screen. |
I also cleaned up the package itself. The CodeCanyon download shipped with the developer’s hidden .git folder inside it, with file paths long enough that Windows refuses to unzip it. Those leftovers are gone from our build.
Running Lumise? Do These Four Things Today
- Check your version. Go to Plugins in wp-admin. If Lumise shows 2.1.2 or lower, you are affected.
- Turn it off if you can. Deactivating Lumise until a fix ships is the only complete protection. If the designer drives your sales, get a firewall rule in place instead. Patchstack has published a mitigation rule for this one.
- Look for signs of a break-in. Open
wp-content/uploads/lumise_data/user_data/and look for image files that won’t open as images. A “picture” that is really text, especially one starting with<?php, is a red flag. If you find one, change your database password and your WordPress security keys right away. - Push the developer. Comment on the CodeCanyon item page and contact Lumise support. Expired support doesn’t matter here, because security updates go to every buyer.
We checked our client’s upload folder file by file and found no sign the bug had been used.
Plugins Are Only as Safe as Their Last Update
Premium plugins from marketplaces are great until the developer goes quiet. This one hadn’t been updated since July, and the fix for an earlier security report still hadn’t shipped. Somebody has to be watching, and when the vendor is slow, somebody has to be able to open the code and fix it.
That’s the job for our website care clients. We monitor every site for vulnerability alerts, patch what we can the same day, and tell you in plain English what happened. If you run Lumise or any other WooCommerce plugin and aren’t sure where you stand, reach out to Montarev and we’ll take a look.