CVE-2026-4420: Stored XSS in Bludit page creation tags field
- Vendor
- Bludit
CVE-2026-4420 is a stored cross-site scripting vulnerability in the Bludit CMS page creation functionality. An authenticated user with page creation privileges, including roles such as Author, Editor, or Administrator, can inject malicious JavaScript into the tags field when creating a new article. The payload is then stored by the application and executed in a victim’s browser when the victim visits the URL of the created resource. The resource itself is accessible without authentication. Based on the provided content, versions 3.17.2 and 3.18.0 were tested and confirmed vulnerable; other versions were not tested and may also be affected.
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 attacker to execute arbitrary JavaScript in the browser context of users who view the malicious page. This can enable session theft, unauthorized actions performed as the victim, and administrative compromise through browser-mediated actions. The provided content specifically notes that the flaw could be used to automatically create a new site administrator if the victim has sufficient privileges, making full application compromise possible when a privileged user is targeted.
Mitigation
If you can’t patch tonight, do this now.
Until an official fix is available, restrict page creation privileges to only fully trusted users, review and remove malicious content from existing pages, and monitor for suspicious article creation or unexpected administrator account creation. Apply strict server-side sanitization and output encoding for the tags field if local code modification is possible. Additional browser-side hardening such as a restrictive Content Security Policy may reduce exploitability, though it should not be considered a complete fix for stored XSS.
Remediation
Patch, then assume compromise.
Upgrade to a vendor-fixed version once one is made available. Because the vendor did not provide a vulnerable version range or remediation details in the supplied content, the precise fixed version is currently not available. The underlying issue should be remediated by properly validating and output-encoding untrusted input from the tags field in the page creation workflow and ensuring stored content cannot introduce executable script into rendered pages.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-4420 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-4420 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-4420?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-4420.
- Is there a patch for CVE-2026-4420?
- Upgrade to a vendor-fixed version once one is made available. Because the vendor did not provide a vulnerable version range or remediation details in the supplied content, the precise fixed version is currently not available.
- What products are affected by CVE-2026-4420?
- Bludit.
- How severe is CVE-2026-4420?
- CVE-2026-4420 has a CVSS v4 score of 5.1 (Medium) and an EPSS score of 0.16% (6th percentile) as of Sep 25, 2026.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.