Skip to main content
Mallory
MediumVulnerability

CVE-2026-18478: Stored XSS in Magnolia CMS Import Functionality

Published Aug 10, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.1Medium · v4
EPSS0.46%40th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-18478CWE-79 · Improper Neutralization of Input…

CVE-2026-18478 is a stored cross-site scripting vulnerability in Magnolia CMS affecting the import functionality. In affected Magnolia CMS 6.3.x versions, an attacker with editor privileges can inject arbitrary HTML and JavaScript into the name of an uploaded image during import. The malicious payload is stored by the application and is rendered and executed in the browser when the uploaded image is opened. This results from improper neutralization of untrusted input before web page generation.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated attacker with editor-level access to execute arbitrary script in the context of a victim user's browser when the malicious image entry is viewed or opened. This can enable session theft, execution of unauthorized actions on behalf of the victim, content manipulation, and access to data available within the affected web application context.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict editor-level access to trusted users only, closely monitor and review imported media content and metadata, and apply input validation and output encoding controls around user-supplied image names wherever they are rendered. Limiting access to the vulnerable import workflow can reduce exposure until the fixed version is deployed.

Remediation

Patch, then assume compromise.

Upgrade Magnolia CMS to version 6.3.10 or later, which contains the fix for this vulnerability.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-18478 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-18478 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-18478?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-18478.
Is there a patch for CVE-2026-18478?
Upgrade Magnolia CMS to version 6.3.10 or later, which contains the fix for this vulnerability.
How severe is CVE-2026-18478?
CVE-2026-18478 has a CVSS v4 score of 5.1 (Medium) and an EPSS score of 0.46% (40th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.