CVE-2026-86644: star7th showdoc API Page Save Endpoint editormd.js cross site scripting

Published Sep 8, 2026
·
Updated

A vulnerability was determined in star7th showdoc up to 3.9.1. This vulnerability affects unknown code of the file websrc/public/editor.md/editormd.js of the component API Page Save Endpoint. Executing a manipulation can lead to cross site scripting. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 3.9.2 is able to resolve this issue. This patch is called a8ea1520850b4242f395247f72e87e597506cef0. Upgrading the affected component is recommended. The vendor confirms: "The fix [...] sets Mermaid securityLevel to strict, disables htmlLabels, and sanitizes rendered SVG with DOMPurify."

Affected Software

1 affected component
star7th ShowDoc<=3.9.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade star7th showdoc API Page Save Endpoint editormd.js to a version that resolves this vulnerability.

    Fixed in 3.9.2Patch a8ea1520850b4242f395247f72e87e597506cef0
  2. Configuration

    Apply the vendor fix to set Mermaid `securityLevel` to `strict` to prevent unsafe rendering that could lead to cross site scripting.

    Mermaid (used by showdoc editor) securityLevel = strict
  3. Configuration

    Apply the vendor fix to disable Mermaid `htmlLabels`.

    showdoc Mermaid renderer htmlLabels = disabled
  4. Configuration

    Apply the vendor fix to sanitize rendered SVG using DOMPurify.

    showdoc rendered SVG handling (DOMPurify) DOMPurify sanitization = enabled

Event History

Sep 8, 2026
CVE Published
via MITRE·01:30 PM
Data Sourced
via MITRE·01:30 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which ShowDoc installations are affected?

Star7th ShowDoc versions up to and including 3.9.1 are affected. Version 3.9.2 resolves the issue.

2

What access and interaction does exploitation require?

The issue can be attacked remotely, but the published severity vector indicates an attacker needs low-level privileges and user interaction. Successful exploitation can affect integrity, while no confidentiality or availability impact is identified.

3

What should be done if upgrading is not immediately possible?

The provided data identifies version 3.9.2 as the remediation and recommends upgrading the affected component. Its fix sets Mermaid securityLevel to strict, disables htmlLabels, and sanitizes rendered SVG with DOMPurify.

4

Is public exploit information available?

Yes. The exploit has been publicly disclosed and may be used.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203