1-minute read of a 4 min report

Thelia back-office flaws expose store servers to code execution

By

1-minute read

What a defender needs to know

Thelia 2.6.0 and 2.6.1 expose several back-office routes to server code execution, CERT/CC reports. An administrator can abuse message templates in 2.6.0, mismatched document upload/update validation, banner uploads or module installation. In 2.6.1, translation editing can combine a write outside templates/ with PHP injection; another flaw lets an authorized user submit an absolute path for Smarty to compile. Some routes require particular permissions or filesystem conditions. A stolen admin login is especially consequential on a store where those workflows are reachable.

The note also covers admin-session script injection, a shopper redirect and admin-username enumeration. CERT/CC says a patch for its 2.6 findings is not yet available. A separate 3.0.0 back-office Twig email-template flaw, CVE-2026-107248, is fixed in thelia/twig-engine-module 1.0.9.

Check the running store and module versions. Restrict the Thelia administrative interface to a trusted management path, limit accounts allowed to edit templates and translations or upload files and modules, and remove PHP execution from user-writable directories wherever possible. Rate-limit admin login and forgotten-password requests at the reverse proxy. Verify that PHP cannot execute from writable upload directories; retain the tested control state with the running version. Inspect admin sign-ins, changed templates and modules, and unexpected PHP files if back-office access may have been abused. Verify admin reachability from an untrusted network, actual account permissions and the installed 3.0.0 Twig module version; keep the 2.6 restrictions until a supported fix is verified.

Primary sources