Zenthas

Mermaid Export Ready: Security

Version 1.4.0, 7 November 2026.

Architecture

A Forge Custom UI macro on Node.js 24 (arm64). Mermaid 12.2.0 is bundled and pinned, and rendering happens in the sandboxed Forge iframe. Two functions exist: a resolver for Jira and attachment reads, and an export function for PDF export. There is no database and no storage.

Data and egress

The app declares no external egress and does not call external services. The viewer talks only to Atlassian. Loading a source from a URL is not offered.

Permissions

read:attachment:confluence: find the export snapshot and list .mmd and .md sources attached to the page.
write:attachment:confluence: write snapshot attachments to the page.
write:confluence-file: upload the PNG and SVG snapshot. The upload endpoint exists only in the classic API, which requires this scope.
read:jira-work: read issues for the Jira source, always as the viewing user.

The app requests no page read scope and no user data scope.

Controls

Jira and attachment calls run as the viewing user. The export function runs as the app only to look up the snapshot attachment of the page being exported. Mermaid runs at the strict security level, with no click handlers or scripts, and labels are plain text. Inputs are validated: epic key and attachment id by pattern, JQL and source length limited, at most 150 issues. The editor runs in a Shadow Root so the Forge content security policy stays strict. Automated tests cover rendering, configuration, Jira mapping, errors, backend and UI.

Known limits

Old snapshot attachments are not removed automatically. Snapshots are created in the browser, so a page that was never opened has no snapshot. Frozen Jira diagrams contain issue text visible to everyone who can view the page.

Report a vulnerability

Write to support@zenthas.com. We acknowledge every report, and fixes ship as new app versions through Atlassian Marketplace.