Template Tags

Template tags are placeholders in your Word template that get replaced with real data on export.

Tag Syntax

Report Fields

Dynamic Narrative Sections

Narrative tab sections become template tags based on their slugified title (lowercased, non-alphanumeric → underscore).

A section titled "Introduction" becomes:

• {~report.introduction} — HTML formatted
• {report.introduction_plain} — plain text

A section titled "Technical Summary" becomes:

• {~report.technical_summary} — HTML formatted
• {report.technical_summary_plain} — plain text

Scope tab sections follow the same pattern: {~report.scope} / {report.scope_plain}, {~report.limitations} / {report.limitations_plain}, etc.

Client Fields

Project Fields

Organization & Metadata

Consultants

Loop: {#consultants}...{/consultants}

Pre-joined: {consultantNames}

All consultant names joined with commas — useful for a single table cell.

Findings

Top-Level Finding Loops

These contain ALL findings across all tabs.

Severity-Filtered Loops

Only findings of that severity. Empty arrays are falsy — content is skipped when no findings match.

Finding Count

{findingCount} — total count. Use {#findingCount}...{/findingCount} as a conditional (0 is falsy, skips content).

Fields Inside Any Finding Loop

Available inside {#findings}, {#findingsBySeverity}, {#criticalFindings}, etc.

CVSS Fields

Findings can carry two independent CVSS records — v3.1 and v4.0 — and a finding may have either, both, or neither. The "main" {cvss*} tags follow the tab's sort order so template columns reflect whichever version the user picked. Explicit per-version tags are available when a column must be pinned to one version.

Active CVSS (follows the tab's sort toggle)

{cvssScore}, {cvssVector}, {cvssSeverity}, {hasCvss} resolve to:

• 3.1 when the tab's sort order is Severity or CVSS 3.1 (default)
• 4.0 when the tab's sort order is CVSS 4.0

Explicit CVSS v3.1

Always pinned to CVSS 3.1 regardless of sort order.

Explicit CVSS v4.0

Always pinned to CVSS 4.0 regardless of sort order.

Evidence Loop (nested inside findings)

{#evidence}...{/evidence} — only uploaded evidence (not pasted images).

Affected Assets Loop (nested inside findings)

{#affectedAssets}...{/affectedAssets}

Tabs

Tab Loops

Fields Inside Tab Loops

Per-Tab Finding Loops

Inside {#tabs}, these iterate that tab's findings only:

{#findings}, {#findingsBySeverity}, {#findingsByCvss}, {#findingsByCvss3}, {#findingsByCvss4}, {#criticalFindings}, {#highFindings}, {#mediumFindings}, {#lowFindings}, {#infoFindings}

All finding fields from the tables above are available inside these loops.

Per-Tab Narrative Sections

Inside {#tabs}, each tab's narrative sections are available as slugified tags:

• {~introduction}, {introduction_plain}
• {~technical_summary}, {technical_summary_plain}
• {~scope}, etc.

Prefix-Scoped Tags

When a tab has a non-"report" prefix (e.g. "appsec"), its data is also available at the top level under that prefix. Useful for templates that don't use tab loops.

Replace appsec with any custom prefix (network, mobile, etc.). When the prefix is report (default), these go under report.*.

Template Patterns

Simple Report

{report.title}
Client: {client.name}
Date: {project.startDate} - {project.endDate}

{~report.executiveSummary}

{#findings}
  {findingId} - {title} ({severity})
  CVSS: {cvssScore}
  {~description}
  {~remediation}
  {#evidence}
    {%image}
    {@captionXml}
  {/evidence}
{/findings}

Tab-Based with Severity Sections

{#tabs}
{#findingCount}
{name} Technical Findings

{#criticalFindings}
  {title} - {cvssScore}
  {~description}
  {~remediation}
{/criticalFindings}

{#highFindings}
  {title} - {cvssScore}
  {~description}
  {~remediation}
{/highFindings}

{#mediumFindings}
  {title} - {cvssScore}
{/mediumFindings}

{#lowFindings}
  {title} - {cvssScore}
{/lowFindings}

{#infoFindings}
  {title} - {cvssScore}
{/infoFindings}
{/findingCount}
{/tabs}

CVSS-Ordered Findings

{#findingsByCvss}
  {order}. {title}
  Severity: {severity} | CVSS: {cvssScore} ({cvssSeverity})
  {#hasCvss}
    Base: {cvssBaseScore} | Temporal: {cvssTemporalScore} | Environmental: {cvssEnvironmentalScore}
    Vector: {cvssBaseCalc}
  {/hasCvss}
  {~description}
{/findingsByCvss}

Prefix-Scoped (Fixed Tabs, No Loop)

AppSec Assessment
{~appsec.introduction}

{#appsec.criticalFindings}
  {title} - {cvssScore}
{/appsec.criticalFindings}

{#appsec.highFindings}
  {title} - {cvssScore}
{/appsec.highFindings}

Consultants Table

Or as a single string: {consultantNames}

Finding Sort Order

The tab's sort order setting controls the order of {#findings}, the {order} / {findingId} assignment, and the active-version {cvssScore} / {cvssVector} / {cvssSeverity} tags.

{#findingsBySeverity}, {#findingsByCvss3}, and {#findingsByCvss4} always use their respective sort regardless of the tab setting. {#findingsByCvss} follows the active CVSS version (same logic as {cvssScore}).

Sort Conditionals

Use these inside a finding loop or at report / tab scope to render different table layouts per sort order. The generic {#isSortedByCvss} is TRUE for either CVSS version so older templates keep rendering when users toggle to 4.0.