CVE-2026-18478: Magnolia CMS · Cross-site Scripting
Affects Magnolia CMSSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 6.3.10 when convenient.
Data as of 8 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.3.10
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade Magnolia CMS to 6.3.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Magnolia DXPMagnolia CMS | Affected
| Fixed in
|
Maveninfo.magnolia/magnolia-cmspkg:maven/info.magnolia/magnolia-cmsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Magnolia CMS version 6.3.10. Users should upgrade to version 6.3.10 or later to remediate the issue. No other official remediation or temporary fixes are documented. Patch status is confirmed by the vendor's versioning information.
Description
Magnolia CMS is vulnerable to Stored XSS in import functionality. An attacker with editor privileges can inject arbitrary HTML and JS into the name of uploaded image, which will be rendered/executed when opening uploaded image. The issue was fixed in version 6.3.10