Q: How to self-check? (Features/Scanning)

🔍 **Check**: Scan for `macro-fullcalendar` version < 2.4.5. 🌐 **Target**: Look for `Calendar.JSONService` endpoints. 📡 **Tools**: Use SQL injection scanners against calendar-related API paths.

Q: Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: Yes. 🔧 **Patch**: Upgrade to **version 2.4.5** or later. 🔗 **Ref**: GitHub Advisory GHSA-2g22-wg49-fgv5 & Commit 5fdcf06.

Q: Is it urgent? (Priority Suggestion)

🔥 **Priority: CRITICAL**. 📊 **CVSS**: 9.8 (High). 🚀 **Action**: Patch immediately. Remote, unauthenticated (or low-priv) SQLi is a top-tier threat.

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: SQL Injection in XWiki Full Calendar Macro.
💥 **Consequences**: Attackers can access sensitive database info or trigger Denial of Service (DoS). Critical integrity/availability loss.

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **CWE-89**: Improper Neutralization of Special Elements used in an SQL Command.
🔍 **Flaw**: User input in the Calendar.JSONService is not sanitized before database execution.

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Product**: XWiki Full Calendar Macro (`macro-fullcalendar`).
📉 **Affected**: Versions **prior to 2.4.5**.
🏢 **Vendor**: xwiki-contrib.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

🕵️ **Data Access**: Read arbitrary database contents.
💣 **DoS**: Crash or overload the service.
🔓 **Privilege**: Requires only 'View Calendar.JSONService' permission.

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

📉 **Threshold: LOW**.
🔑 **Auth**: No authentication required for the specific endpoint if view permission exists (often public or low-barrier).
🌐 **Network**: Remote (AV:N).
🎯 **Complexity**: Low (AC:L).

Question 6

Is there a public Exp? (PoC/Wild Exploitation)

Accepted Answer

🚫 **Public Exploit**: None currently listed in the data.
📝 **Status**: PoCs are empty in the provided dataset.
⚠️ **Risk**: High CVSS score suggests easy exploitation logic, even without public code.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Check**: Scan for `macro-fullcalendar` version < 2.4.5.
🌐 **Target**: Look for `Calendar.JSONService` endpoints.
📡 **Tools**: Use SQL injection scanners against calendar-related API paths.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

✅ **Fixed**: Yes.
🔧 **Patch**: Upgrade to **version 2.4.5** or later.
🔗 **Ref**: GitHub Advisory GHSA-2g22-wg49-fgv5 & Commit 5fdcf06.

Question 9

What if no patch? (Workaround)

Accepted Answer

🛑 **Workaround**: Disable the Full Calendar Macro if not needed.
🚧 **Network**: Restrict access to `Calendar.JSONService` via WAF or firewall rules.…

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Priority: CRITICAL**.
📊 **CVSS**: 9.8 (High).
🚀 **Action**: Patch immediately. Remote, unauthenticated (or low-priv) SQLi is a top-tier threat.

Goal Reached Thanks to every supporter — we hit 100%!

CVE-2025-65091 — AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

Q2Root Cause? (CWE/Flaw)

Q3Who is affected? (Versions/Components)

Q4What can hackers do? (Privileges/Data)

Q5Is exploitation threshold high? (Auth/Config)

Q6Is there a public Exp? (PoC/Wild Exploitation)

Q7How to self-check? (Features/Scanning)

Q8Is it fixed officially? (Patch/Mitigation)

Q9What if no patch? (Workaround)

Q10Is it urgent? (Priority Suggestion)

Continue exploring