Unknown severity · Source severity not reportedCVE-2026-103527

CVE-2026-103527CVE-2026-103527

Answer in brief

CVE-2026-103527 records a Unknown severity vulnerability in CVE-2026-103527. The current sources do not mark it as known exploited. The current feed maps Thelia/Thelia (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 12, 2026Updated Oct 12, 2026Source checked Oct 12, 2026First seen by HOL Oct 12, 2026Material review Oct 12, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Thelia/Thelia (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Thelia/Theliageneric	>=0 <=2.6.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Thelia/Thelia.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Oct 12, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 12, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 12, 2026

Sources and claim methodology

Source referencekb.cert.org

Upstream source description

Thelia v2.6.0's Smarty templates (address.html and address-update.html) fail to properly escape double quotes in the “next” parameter, enabling reflected Cross‑Site Scripting (XSS) when an authenticated user visits the malicious link containing attacker‑controlled JavaScript.

Quoted source text, attributed separately from HOL analysis.