Thelia v2.6.0 contains an open redirect vulnerability in its address creation workflow. After a user accesses a crafted URL and successfully submits the “Add New Address” form, the application redirects them to the URL specified in the next parameter. Because the application does not validate whether the destination belongs to the same origin or an approved allowlist, an attacker can supply an arbitrary external URL and redirect users to an attacker-controlled website.
CVE-2026-103523
- No CVSS published and no exploitation signals yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
The CVE record's CNA (CERT/CC) lists Thelia versions up to and including 2.6.0 as affected. No release containing a fix is confirmed on record.
- CVSS v3
- —
- EchelonGraph score
- Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
- EG Score
- —
- EG Risk
- —
- EPSS PROB
- 0.2%
- EPSS %ILE
- 6th
- KEV
- Not listed
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 12, 2026
Last Modified
October 13, 2026
References (1)
- cret@certhttps://kb.cert.org/vuls/id/162329
Vendor Advisories for CVE-2026-103523(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
- 2026-10-13 14:08 UTCGHSA enrichmentGHSA-2rgp-5p5r-5w94
- 2026-10-12 15:25 UTCNVD update
- 2026-10-12 14:57 UTCEG score recompute
- 2026-10-12 14:55 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-103523?
When was the CVE record for CVE-2026-103523 published?
Is CVE-2026-103523 actively exploited?
How do I remediate CVE-2026-103523?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-103523
Is Your Infrastructure Affected by CVE-2026-103523?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.