CVE-2025-65091
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedXWiki Full Calendar Macro displays objects from the wiki on the calendar. Prior to version 2.4.5, users with the right to view the Calendar.JSONService page (including guest users) can exploit a SQL injection vulnerability by accessing database info or starting a DoS attack. This issue has been patched in version 2.4.5.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe XWiki Full Calendar Macro contains a SQL injection vulnerability in the Calendar.JSONService page, allowing users with view permissions (including guest users) to execute arbitrary SQL queries. This enables attackers to extract sensitive database information or launch denial of service attacks. The vulnerability affects all versions prior to 2.4.5.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.4.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Full Calendar Macro versionIn the XWiki administration interface, navigate to the Extension Manager and locate the Full Calendar Macro extension. Note the installed version number.Affected if The installed version is lower than 2.4.5 (for example, 2.4.4, 2.4.3, or earlier).
-
Verify Calendar.JSONService page existsAccess the page at /xwiki/bin/view/<space>/Calendar.JSONService (replace <space> with the space where the calendar macro is installed, commonly 'FullCalendar' or 'Scheduler'). Check if the page loads without a 'page does not exist' error.Affected if The Calendar.JSONService page exists and is publicly accessible (returns a response rather than a 404 error).
-
Confirm view rights are enabled for guestsIn XWiki administration, check the rights configuration for the Calendar.JSONService page. Verify if the 'view' permission is granted to XWikiGuest (unauthenticated users) or set to 'AllUsers'.Affected if Guest users or unauthenticated visitors have view permissions on the Calendar.JSONService page.
The environment is affected if Full Calendar Macro version is below 2.4.5 AND the Calendar.JSONService page is accessible to users with view rights (including guests).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.4.5
Upgrade the XWiki Full Calendar Macro to version 2.4.5 or later to patch the SQL injection vulnerability. If immediate patching is not possible, restrict or disable access to the Calendar.JSONService page for unauthenticated users.
2.4.5
- Check the current version of Full Calendar Macro extension installed in your XWiki instance
- Upgrade the Full Calendar Macro extension to version 2.4.5 or later
- Verify the upgrade was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65091 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-65091 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data