CVE-2026-55105

7.7

laurent22 · Joplin

Joplin fails to sanitize HTML generated by the Fountain renderer, allowing an attacker to execute arbitrary scripts in the context of the note viewer or published server pages.

Executive summary

A cross-site scripting vulnerability in the Joplin note-taking application allows authenticated attackers to execute arbitrary scripts, posing a significant risk of data exposure.

Vulnerability

This is a cross-site scripting (CWE-79) vulnerability where the application fails to neutralize input within Fountain code blocks, allowing authenticated users to inject malicious scripts into note outputs.

Business impact

The vulnerability carries a CVSS score of 7.7, reflecting a high risk due to the potential for information disclosure. Successful exploitation allows an attacker to read sensitive data loaded in the note viewer or steal session information from authenticated users, which could lead to unauthorized access to the Joplin server environment and broader organizational data compromise.

Remediation

Immediate Action: Update the Joplin application to version 3.6.15 or 3.7.2, which contain the necessary sanitization logic to remediate the flaw.

Proactive Monitoring: Review Joplin Server access logs for unusual script execution patterns or unexpected requests originating from note-rendering components.

Compensating Controls: If immediate patching is not feasible, disable the Fountain rendering feature in desktop, mobile, and server configurations to eliminate the attack vector.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

Given the high CVSS score and the risk of unauthorized data access, organizations should treat this vulnerability with high priority. System administrators must verify their Joplin deployment versions immediately and apply the provided updates to ensure that the Fountain renderer is properly secured against script injection.

More laurent22 CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources