CVE-2025-65090 json
XWiki Full Calendar Macro vulnerable to data leak through Calendar.JSONService
published 2026-01-09 9 mo ago modified 2026-06-17 4 mo ago also GHSA-637h-ch24-xp9m , EUVD-2026-1700
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 20%
- public exploits
- 0
- none known
Summary
XWiki Full Calendar Macro displays objects from the wiki on the calendar. Prior to version 2.4.6, users with the rights to view the Calendar.JSONService page (including guest users) can exploit the data leak vulnerability by accessing database info, with the exception of passwords. This issue has been patched in version 2.4.6.
Patch / fix
- maven org.xwiki.contrib:macro-fullcalendar-pom 2.4.6
- xwiki full_calendar_macro 2.4.6
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 9 mo ago
Exploit prediction
0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.xwiki.contrib:macro-fullcalendar-pom | <2.4.6 |
2.4.6 |
Affected products
- xwiki-contrib macro-fullcalendar
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
github.com
/xwiki-contrib/macro-fullcalendar/commit/25bc14c181c9a92f493b20ac264388c7ba171884
web, patch
-
github.com
/xwiki-contrib/macro-fullcalendar/security/advisories/GHSA-637h-ch24-xp9m
web, third-party-advisory
-
jira.xwiki.org
/browse/FULLCAL-82
web, permissions-required
-
nvd.nist.gov
/vuln/detail/CVE-2025-65090
advisory
-
github.com
/xwiki-contrib/macro-fullcalendar
package
Sources
- CVE List CVE-2025-65090
- GitHub Advisory GHSA-637h-ch24-xp9m
- NVD CVE-2025-65090
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.