CERT/CC Warns of Eleven Vulnerabilities in Thelia 2.6.0 and 2.6.1

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

CERT/CC published VU#162329 for Thelia 2.6.0 and 2.6.1 and reported that a patch was not available. Restrict administrative access, limit upload and template-editing capability, prevent PHP execution in user-writable directories, apply proxy controls, and retain evidence while seeking supported remediation.

Confirm Scope And Apply The Supported Remediation

What to do now: Identify Thelia 2.6.0 and 2.6.1 deployments; restrict administrative interfaces; disable or tightly limit uploads and template editing; remove PHP execution from user-writable paths; apply rate limiting, MIME filtering, and URL allowlisting; monitor exploitation paths; and obtain supported vendor remediation.

Open the authoritative advisory

Last verified: 2026-10-12 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeThelia 2.6.0 and 2.6.1
AdvisoryVU#162329
CVEsCVE-2026-103521, CVE-2026-103522, CVE-2026-103523, CVE-2026-103524, CVE-2026-103526, CVE-2026-103527, CVE-2026-103528, CVE-2026-103529, CVE-2026-103535, CVE-2026-103537, CVE-2026-107248
Authoritative release date2026-10-12 00:00:00 UTC
Authority revision date2026-10-12 14:52:00 UTC
Affected versionsThelia 2.6.0 and 2.6.1 as identified in CERT/CC Vulnerability Note VU#162329.
Fixed versionNo patch was available when CERT/CC published revision 1; apply the authority's access restrictions and hardening measures while obtaining supported vendor remediation
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

CERT/CC documented multiple command-execution, server-side template injection, cross-site scripting, open-redirect, and username-enumeration paths and said coordinated vendor remediation was not available at publication.

What To Validate Now

  1. Inventory. Locate Thelia 2.6.0 and 2.6.1 deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: Thelia 2.6.0 and 2.6.1 as identified in CERT/CC Vulnerability Note VU#162329. Do not infer applicability from product family or severity alone.
  3. Remediate. Apply No patch was available when CERT/CC published revision 1; apply the authority's access restrictions and hardening measures while obtaining supported vendor remediation through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Compensating controls reduce exposure but are not a patch. Test checkout, content, template, upload, administration, and reverse-proxy behavior; preserve web, application, WAF, and authentication logs for investigation. Preserve the authority snapshot, asset and owner records, before-and-after versions, change approval, installation output, validation results, exceptions, and rollback evidence.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.