Quick answers
- Is CVE-2026-88743 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88743 being exploited in the wild.
- How severe is CVE-2026-88743?
- Medium severity, with a CVSS score of 6.1, published 15 September 2026.
- Which products and versions are affected?
- Bacularis 4.7.0 through 6.5.0.
- Is there a fix for CVE-2026-88743?
- A patch was published on 2026: Fixed in version 6.5.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88743 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-88743?
- Check whether you run Bacularis 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
Bacularis versions 4.7.0 through 6.5.0 are vulnerable to stored XSS via the tag name field in Director / Configure director / JobDefs. An attacker can inject a JavaScript payload (e.g., <script>prompt()</script>) into the tag name parameter by intercepting the tag creation request and modifying the JSON payload in the msg_envelope_search parameter. The payload is stored server-side and executed in the browser context of any user who views jobs or navigates the application interface. Attack requires authenticated access to the application but affects any user with job visibility permissions, including normal (non-admin) users. The vulnerability is fixed in version 6.5.1.
Affected products
- Bacularis Bacularis 4.7.0 through 6.5.0
Timeline
- 2026-09-11: disclosed
- 2026: patched: Fixed in version 6.5.1