CVE-2026-120205 Thelia CVE debrief

Who should care

Defenders responsible for Thelia installations, administrators, and security teams should assess exposure and apply patches or mitigations to prevent exploitation. They should also verify Thelia version, monitor for suspicious activity, and review compensating controls for exposed systems. Security teams should prioritize verifying exposure and applying patches or mitigations to prevent exploitation, and also consider implementing additional security措施 to

Why it matters

CVE-2026-120205 is a stored cross-site scripting vulnerability in Thelia before 3.1.0 that allows unauthenticated attackers to inject scripts via customer names, potentially leading to CSRF token theft and administrator account creation. Defenders should verify exposure, apply patches, and monitor for suspicious activity.

• Potential theft of CSRF tokens
• Possible creation of administrator accounts
• Required verification of Thelia version and exposure
• Necessity to monitor for suspicious activity

Technical summary

Thelia before 3.1.0 contains a stored cross-site scripting vulnerability in ForSomeCustomers::getSummary() due to unescaped customer names. Attackers can register with a script payload as their name that executes when administrators view related coupons, potentially leading to CSRF token theft and administrator account creation. The vulnerability exists in the ForSomeCustomers::getSummary() function, which does not properly sanitize customer input, allowing for malicious script injection. Defenders should prioritize verifying exposure and applying patches or mitigations to prevent exploitation.

Defensive priority

Defenders should prioritize verifying exposure and applying patches or mitigations to prevent exploitation.

Recommended defensive actions

• Verify Thelia version and apply patch to 3.1.0 or later
• Restrict access to ForSomeCustomers::getSummary()
• Monitor for suspicious administrator account creation
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability was reported by [email protected] and is documented in various source references, including GitHub commits and releases. Thelia versions before 3.1.0 are affected, and defenders should verify exposure and apply patches or mitigations. Evidence is limited to public source references and may not reflect the full scope or impact of the vulnerability.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.