Skip to content

Cross Site Scripting in recurrent event title

High
ChiuchiuSorin published GHSA-wfqm-4f92-8m4j Dec 12, 2025

Package

maven com.xwiki.mocca-calendar:application-mocca-calendar (Maven)

Affected versions

<= 2.15.4

Patched versions

2.16.0

Description

Impact

Everyone who has edit rights on the calendar page is susceptible to the attack, running any possibly malicious javascript/html/css code.

Details

Any user allowed to view the calendar page, may edit an instance of a recurrent event and set a title such as: this is an XSS vulenrability<script>alert(1)</script>, which will show fine in the Calendar UI. The script gets executed when opening the event modal and going to edit mode, missing the script part from the title. When simply viewing the event through the modal in the calendar page, the script doesn't seem to get executed, and the script part of the title is visible.

Workarounds

Do not open events with a suspicious title and immediately delete them.

PoC

  1. Install and activate the Mocca Calendar app
  2. Create a recurrent event.
  3. Edit an instance of the recurrent event and add a title such as: <script>alert(1)</script>
  4. Open the edited event instance modal and press the Edit button

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:H

CVE ID

CVE-2025-67831

Weaknesses

No CWEs