Skip to content

Cross Site Scripting in the Event view page

High
ChiuchiuSorin published GHSA-fjv4-pgh9-jfgc Jul 30, 2025

Package

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

Affected versions

<= 2.14.2

Patched versions

2.15

Description

Summary

The title is not properly escaped in the view event page, allowing XSS for any user with view rights on the page, just by creating or editing an event and giving a script.

Details

Any user allowed to view the calendar page may create an event with a title as this is an XSS vulenrability<script>alert("hi!")</script>, which will show fine in the Calendar UI, but when opening the event page, the script gets executed and the title is missing the script part. When editing the event through the modal in the calendar page, the script doesn't seem to get executed, but the script part of the title is missing.
The code in the MoccaCalendarEventSheet view mode branch is not escaped. The code to be escaped is $eventInstance.getTitle() in the #else branch of #if($isEdit).

PoC

  1. Install and activate the Mocca Calendar app
  2. Create an event titled <script>alert("hi!")</script> (any new user can do this)
  3. Open the event page in a new tab
  4. The page will run the script before fully loading the content

Workarounds

Before opening an event page, check its title either by looking in the navigation tree, or by looking at the day view inside the calendar to have the title fully displayed. Delete any event that contains suspicious text.

Impact

Everyone who views the event page is susceptible to the attack, running any possibly malicious javascript/html/css code.

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-52132

Weaknesses

No CWEs