Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-103535 Overview
CVE-2026-103535 affects Thelia v2.6.1, an open-source e-commerce platform. The vulnerability combines a path traversal flaw and a PHP code injection flaw in the translation editor. An authenticated user with UPDATE permissions on admin.configuration.language can chain both weaknesses to achieve remote code execution. The item_name parameter does not sanitize ../ sequences when constructing the translation file write path. The translation-writing logic also fails to escape backslash characters in user-supplied values, allowing input to break out of the PHP string literal. Combined, these flaws enable an attacker to write a malicious PHP file to a web-accessible path and execute it with the web server's privileges.
Critical Impact
Authenticated attackers can achieve remote code execution on the underlying web server, leading to full application compromise.
Affected Products
- Thelia v2.6.1
- Earlier Thelia v2 branches sharing the vulnerable translation editor logic
- Deployments exposing the admin configuration interface to untrusted users
Discovery Timeline
- 2026-10-12 - CVE-2026-103535 published to NVD
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-103535
Vulnerability Analysis
The vulnerability is a chained flaw classified under [CWE-94] Improper Control of Generation of Code (Code Injection). It resides in the Thelia administrative translation editor, which writes PHP translation files based on user-supplied input. Two distinct weaknesses combine to produce remote code execution.
The first weakness is a path traversal issue in the item_name request parameter. Thelia uses this value to construct the destination path for the translation file. Because ../ sequences are not stripped or rejected, an attacker can redirect the write operation outside the intended templates/ directory. Web-accessible locations such as the document root are reachable targets.
The second weakness is improper escaping of backslash characters in translation values. The writer serializes values into a PHP string literal without escaping \, so a crafted value can terminate the literal early. Once the literal is broken, subsequent characters are interpreted as PHP code when the file is loaded.
Root Cause
The root cause is missing input sanitization in two code paths that handle attacker-controlled data. Filename construction trusts item_name without canonicalization, and value serialization trusts translation strings without escaping backslashes or validating content against the target language syntax.
Attack Vector
Exploitation requires an authenticated session with UPDATE privileges on admin.configuration.language. The attacker submits a crafted translation entry where item_name contains traversal sequences pointing to a web-accessible directory, and the translation value contains a backslash-terminated PHP payload. Thelia writes the resulting file to the attacker-controlled location. A subsequent HTTP request to the written file triggers execution of the injected PHP under the web server account.
No verified proof-of-concept code is published. See the CERT Vulnerability Advisory #162329 for technical details.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-103535
Indicators of Compromise
- Translation editor requests containing ../ or encoded traversal sequences in the item_name parameter.
- Newly created .php files outside the Thelia templates/ directory, especially under web-accessible paths.
- Translation files containing unexpected backslashes, PHP tags, or executable constructs within string values.
- Web server access logs showing requests to unfamiliar PHP files immediately after an admin translation save event.
Detection Strategies
- Review web server and PHP-FPM logs for PHP execution originating from paths outside the Thelia application code directories.
- Monitor the Thelia admin audit trail for admin.configuration.language UPDATE actions by non-standard accounts.
- Compare the file system state of the Thelia webroot against a known-good baseline to flag unexpected PHP files.
Monitoring Recommendations
- Alert on file-write events to .php targets originating from the PHP-FPM or Apache process serving Thelia.
- Capture and inspect HTTP POST bodies to the translation editor endpoint for traversal patterns.
- Correlate authentication events for privileged admin accounts with subsequent translation editor activity.
How to Mitigate CVE-2026-103535
Immediate Actions Required
- Restrict access to the Thelia admin interface using network controls, IP allowlisting, or VPN requirements.
- Audit all accounts that hold UPDATE permission on admin.configuration.language and remove unnecessary privileges.
- Rotate credentials for administrative accounts and review recent translation editor activity for anomalies.
- Scan the Thelia webroot for unexpected .php files written outside the application's standard directories.
Patch Information
No fixed version is referenced in the NVD entry at the time of publication. Consult the CERT Vulnerability Advisory #162329 and the Thelia project for upstream remediation status before upgrading production deployments.
Workarounds
- Remove or restrict UPDATE permission on admin.configuration.language to the smallest possible set of trusted administrators.
- Configure the web server to deny PHP execution outside the designated Thelia application directories.
- Place the admin interface behind an authenticating reverse proxy that enforces additional access controls.
- Enable file integrity monitoring on the Thelia installation to detect unauthorized file writes.
# Example nginx configuration to restrict PHP execution to the Thelia web directory
location ~ \.php$ {
# Only allow PHP execution under the intended application path
if ($request_filename !~ "^/var/www/thelia/web/") {
return 403;
}
fastcgi_pass unix:/run/php/php-fpm.sock;
include fastcgi_params;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

