Quick answers
- Is CVE-2026-41456 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41456 being exploited in the wild.
- How severe is CVE-2026-41456?
- Informational severity, with a CVSS score of 5.1, published 21 April 2026.
- Which products and versions are affected?
- Bludit <= 3.20.
- Is there a fix for CVE-2026-41456?
- A patch was published on 2026-04-19: Fix submitted via pull request 1691 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41456 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-41456?
- Check whether you run Bludit at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A reflected cross-site scripting (XSS) vulnerability exists in Bludit CMS versions up to 3.20 within the search plugin. The root cause is the improper neutralization of user-supplied input before it is rendered in the search results page, specifically failing to HTML-escape search terms and URLs. An unauthenticated remote attacker can exploit this by crafting a URL containing a malicious JavaScript payload in the search query parameter. If a victim visits this URL, the script executes in their browser context, potentially allowing for session cookie theft or unauthorized actions. The issue is resolved in commit 6732dde by implementing context-aware HTML escaping using htmlspecialchars.
Affected products
- Bludit Bludit CMS <= 3.20
Timeline
- 2026-04-19: patched: Fix submitted via pull request 1691
- 2026-04-21: disclosed: Vulnerability details and CVE published