Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain admin Thelia credentials
-
DeliverySubmit malicious PHP via document update endpoint
-
ExploitBypass missing executable-type validation
-
ExecutionRequest uploaded script via web server
-
ImpactExecute arbitrary code on host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK
2 techniques across 2 tactics: Command and Control, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated account with administrative Thelia permissions (CVSS PR:H) and specifically abuses the document UPDATE endpoint in Thelia v2.6.0, which - unlike the document UPLOAD endpoint - fails to validate/block executable file types (CWE-434). The attacker must be able to reach the admin interface over the network (AV:N) and upload a server-executable file such as a PHP script, then invoke it via the web server to gain RCE. Limiting factors: this is not reachable by anonymous/unauthenticated users; it depends on the attacker first holding admin-level access, and on the server being configured to execute uploaded PHP files from the writable document location. No end-user interaction is required (UI:N). |
| Impact | This is a genuine but access-gated risk. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 7.2 High) shows a network-reachable, low-complexity flaw with full confidentiality, integrity, and availability impact - consistent with remote code execution. The critical limiter is PR:H: exploitation requires an authenticated account with administrative Thelia permissions, which substantially narrows the realistic attacker population to insiders, compromised admin credentials, or chained attacks. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so the correct exploitation status is 'no public exploit identified at time of analysis'; there is no evidence of active or widespread exploitation. There is no SSVC decision data in the input to cross-reference. The signals are internally consistent (the description's 'administrative permissions' matches PR:H; the RCE outcome matches C:H/I:H/A:H), so no contradiction needs flagging - the main caveat is that this is an admin-authenticated weakness, which makes it a post-authentication RCE / privilege-abuse issue rather than a wormable internet-facing threat. Treat it as a meaningful-but-not-emergency priority: patch promptly, but it is not a high-urgency mass-exploitation candidate absent POC or KEV evidence. |
| Exploit ScenarioDerived | An attacker who already holds administrative Thelia credentials (via compromise, insider access, or a chained privilege escalation) uses the document update endpoint - which skips the executable-type validation enforced on the upload endpoint - to replace or update a document with a malicious PHP script. They then request that script through the web server to execute arbitrary code on the host. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Remote code execution in Thelia v2.6.0 is achievable by an authenticated administrator who abuses the document update endpoint to upload a server-executable file such as a PHP script. The document upload endpoint correctly blocks executable file types, but the update path omits the same validation (CWE-434), so the flaw is a validation gap between two sibling features rather than a broken upload filter overall. Exploitation is access-gated: the CVSS vector (AV:N/AC:L/PR:H/UI:N) confirms network reachability but requires high-privilege Thelia admin credentials, and the server must actually execute PHP from the writable document location; impact is rated high for confidentiality, integrity, and availability, but no public exploit code or confirmed active exploitation was identified at time of analysis.
RemediationAI
No vendor-released patch identified at time of analysis, and no fix version was supplied in the available intelligence - treat the CERT/CC note (https://kb.cert.org/vuls/id/162329) as the tracking reference and confirm with the Thelia project whether a corrected release has been issued before assuming exposure. Until a fix is available, the highest-value compensating control is to eliminate the execution path: store the document directory outside the web root, or disable script execution there (Apache: remove the PHP handler for that directory or set php_flag engine off; nginx: a location block matching the upload path that returns 403 for .php/.phtml/.phar) - the trade-off is that any legitimate dynamic content served from that path will break, so verify the storefront still functions. Secondary measures: enforce a strict server-side extension and MIME allowlist on the document update endpoint specifically (the gap the vendor already closed on the upload endpoint), restrict and audit Thelia administrator accounts since exploitation requires PR:H admin access, and deploy a WAF rule that inspects multipart uploads to admin document routes for executable extensions - noting WAF rules are bypassable via encoding tricks and should not be the sole control. Add file-integrity monitoring or an alert on newly created .php files inside the documents/upload directory, which will detect exploitation attempts even after a patch is applied.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-434 (Unrestricted Upload of File with Dangerous Type), an input-validation class in which the application fails to enforce an allowlist of safe file extensions or MIME types before persisting user-supplied content to a location the web server can execute. Thelia is a PHP-based e-commerce/content platform, so the document feature stores uploaded files in a web-accessible directory; because PHP is interpreted by the web server, a file ending in .php (or .phtml/.phar depending on configuration) becomes executable code rather than inert content. The defining characteristic here is an inconsistent control: the create/upload endpoint applies the executable-type block, while the update endpoint for the same document object does not, meaning an attacker only needs to create a benign document and then replace its file via the unguarded update route. The CPE string cpe:2.3:a:thelia:thelia:*:*:*:*:*:*:*:* is version-agnostic, but the description and assessment both pin the behavior to Thelia v2.6.0. No CVSS temporal or environmental factors, and no weaponized tooling, are indicated in the available intelligence.
Know when Thelia gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Admin privileges are required to reach the update endpoint, so PR:H; it is network-reachable with no added complexity or user interaction (AV:N/AC:L/UI:N), and RCE yields full C:H/I:H/A:H.
Primary rating from Vendor (certcc).
CVSS VectorVendor: certcc
DescriptionCVE.org
In Thelia v2.6.0, the document upload endpoint properly blocks the upload of executable file types, but the document update endpoint does not perform the same validation. An attacker with administrative Thelia permissions can exploit this vulnerability to upload arbitrary executable files, such as malicious PHP scripts, to achieve remote code execution on the underlying server.
Articles & Coverage 1
Executive ViewAI
Thelia v2.6.0 has a high-severity remote code execution flaw that could allow an authenticated high-privilege administrator to run unauthorized server-side code, potentially compromising the e-commerce platform and its data. The greatest risk is to organizations with broad admin access, shared credentials, or internet-exposed administrative interfaces, because abuse could disrupt storefront operations, expose customer information, and damage brand trust. No vendor-released patch identified at time of analysis, and no public exploit identified at time of analysis, so leadership should prioritize access hardening, upload controls, and monitoring while planning a supported upgrade.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting Thelia admin access to trusted IP ranges or VPN, enforcing MFA, rotating admin credentials, disabling or tightly restricting the document update endpoint, blocking executable upload extensions at the WAF and web server, disabling PHP execution in writable document upload directories, implementing file integrity monitoring and alerting for new web-accessible scripts, and auditing administrator activity for suspicious upload or update events.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Authenticated back-office users of Thelia through 2.6.1 can chain a path traversal flaw in the translation editor with a
Server-side template injection in the back-office Email/Messages feature of Thelia 3.0.0 lets an authenticated user hold
Remote code execution in the Thelia e-commerce platform (all versions before 3.1.2 and 3.2.x before 3.2.1) allows an aut
Authenticated attackers holding a Thelia administrator account can achieve remote code execution on the underlying serve
An open redirect in Thelia's address-creation workflow (versions up to and including 2.6.0) lets an attacker craft a URL
Reflected cross-site scripting in Thelia versions up to 2.6.0 allows remote attackers to execute arbitrary JavaScript in
Authenticated administrators of Thelia 2.6.0 and earlier can achieve remote code execution by injecting malicious Smarty
Authenticated template injection in Thelia versions up to and including 2.6.1 lets a logged-in user with access to Smart
Remote code execution in Thelia 2.6.0 and earlier is achievable by an authenticated back-office administrator who uses t
Stored cross-site scripting in Thelia (all versions from 0 through 2.6.0) lets an authenticated back-office user - speci
Username enumeration in Thelia 2.6.0 lets unauthenticated remote attackers determine which administrator accounts exist
CSV formula injection in Thelia (before 3.1.2 and 3.2.0 through 3.2.0, fixed in 3.2.1) lets unauthenticated visitors pla
EUVD-2026-97474
GHSA-pmj2-2x2v-fqcm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB