Description
Thelia 2.6.1 contains an absolute path traversal vulnerability in its Smarty template handling that enables SSTI and remote code execution. The `checkTemplate()` validation restricts relative directory traversal sequences such as `../` but does not reject absolute paths, allowing an authorized user to supply an arbitrary filesystem path as a template. Smarty then loads and compiles the referenced file without an effective security policy, so depending on filesystem layout and deployment configuration, template code in the file can be executed with the web server's privileges.
Published: 2026-10-12
Score: 5.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Remote Code Execution via template traversal
Action: Patch Now
AI Analysis

Impact

The vulnerability resides in Thelia 2.6.1’s template handling. When a user supplies an absolute file path to Smarty, the checkTemplate() function permits it, enabling the template engine to load and compile arbitrary files from the server. Because the template is processed with the same privileges as the web server, an attacker who can supply such a path can inject and execute code, resulting in remote code execution on the host. This flaw is fundamentally a path traversal combined with server side template injection (SSTI), allowing full control over the server process.

Affected Systems

The affected product is Thelia, a free–open source e‑commerce platform based on PHP and Smarty. The flaw is present in version 2.6.1 and any earlier release that does not include the patch for the absolute path validation. The issue is exploitable whenever the application allows authenticated users to edit or upload templates via the front‑end or admin interface, giving them the ability to specify an arbitrary absolute filesystem path.

Risk and Exploitability

No CVSS or EPSS score is publicly defined for this CVE, and it is not listed in the CISA KEV catalog, so the exact numeric risk cannot be quantified. Nevertheless the flaw permits arbitrary code execution with the web server’s privileges; if the server runs as a privileged user, escalation is possible. The attack vector requires an attacker to be an authorized user or to compromise the authentication system. Because the vulnerability exists in web‑accessible code paths and no specific mitigations are provided by the CNA, the practical exploitation likelihood is high once the attacker has legitimate access. Rapid patching or configuration hardening is recommended.

Generated by OpenCVE AI on October 12, 2026 at 16:43 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Thelia to the latest stable version, which includes a fix for validation of absolute template paths.
  • If an upgrade is not immediately feasible, configure the application to restrict template file access to a dedicated directory by using a whitelist of allowed paths and disable the ability for users to specify absolute paths.
  • Ensure the web server user running Thelia has the least privileges required and remove read permissions to system directories from the web user so that even if RCE occurs, the attacker’s scope is limited.

Generated by OpenCVE AI on October 12, 2026 at 16:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

References
History

Thu, 15 Oct 2026 18:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-1336
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 13 Oct 2026 07:45:00 +0000

Type Values Removed Values Added
First Time appeared Thelia
Thelia thelia
Vendors & Products Thelia
Thelia thelia

Mon, 12 Oct 2026 17:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-20
CWE-94

Mon, 12 Oct 2026 15:15:00 +0000

Type Values Removed Values Added
Description Thelia 2.6.1 contains an absolute path traversal vulnerability in its Smarty template handling that enables SSTI and remote code execution. The `checkTemplate()` validation restricts relative directory traversal sequences such as `../` but does not reject absolute paths, allowing an authorized user to supply an arbitrary filesystem path as a template. Smarty then loads and compiles the referenced file without an effective security policy, so depending on filesystem layout and deployment configuration, template code in the file can be executed with the web server's privileges.
Title CVE-2026-103537
References

cve-icon MITRE

Status: PUBLISHED

Assigner: certcc

Published:

Updated: 2026-10-15T17:06:23.101Z

Reserved: 2026-09-30T19:07:13.961Z

Link: CVE-2026-103537

cve-icon Vulnrichment

Updated: 2026-10-15T17:05:13.860Z

cve-icon NVD

Status : Deferred

Published: 2026-10-12T15:17:06.667

Modified: 2026-10-15T18:17:22.200

Link: CVE-2026-103537

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-13T07:26:59Z

Weaknesses
  • CWE-1336

    Improper Neutralization of Special Elements Used in a Template Engine

  • CWE-20

    Improper Input Validation

  • CWE-94

    Improper Control of Generation of Code ('Code Injection')