Q: What can hackers do? (Privileges/Data)

🔓 **Impact**: Full **Remote Code Execution**. 👑 **Privileges**: High! Complete control over the server, data theft, and system modification.

Q: Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: **LOW**. 🌐 **Access**: Network-accessible (AV:N), Low Complexity (AC:L), No Auth Required (PR:N).

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

🧪 **Exploit Status**: No public PoC listed in data. ⚠️ **Risk**: CVSS 9.8 (Critical) suggests high exploitability potential despite no public code yet.

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

🔍 **Check**: Scan for **xwiki-pro-macros** component. 🔎 **Version**: Verify if version is **older than 1.26.5**.

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

✅ **Fix**: Upgrade to **version 1.26.5 or later**. 🔗 **Ref**: See GitHub Advisory GHSA-48f4-h726-74p5.

Q: What if no patch? (Workaround)

🚧 **Workaround**: If unpatched, **disable** the vulnerable macro or restrict network access to the XWiki instance immediately.

Q: Is it urgent? (Priority Suggestion)

🔥 **Priority**: **CRITICAL (S1)**. 🏃 **Action**: Patch immediately. CVSS 9.8 + No Auth = High risk of automated exploitation.

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: A critical Remote Code Execution (RCE) flaw in **xwiki-pro-macros**.
💥 **Consequences**: Attackers can inject malicious code via unescaped `classes` parameters, leading to full system compromise.

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: **CWE-95** (Improper Neutralization of Code).
❌ **Flaw**: Missing escaping for the `classes` parameter allows raw code injection.

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Affected**: **xwiki-pro-macros** by XWiki SAS.
📉 **Versions**: All versions **< 1.26.5**.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

🔓 **Impact**: Full **Remote Code Execution**.
👑 **Privileges**: High! Complete control over the server, data theft, and system modification.

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

⚡ **Threshold**: **LOW**.
🌐 **Access**: Network-accessible (AV:N), Low Complexity (AC:L), No Auth Required (PR:N).

Question 6

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

Accepted Answer

🧪 **Exploit Status**: No public PoC listed in data.
⚠️ **Risk**: CVSS 9.8 (Critical) suggests high exploitability potential despite no public code yet.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Check**: Scan for **xwiki-pro-macros** component.
🔎 **Version**: Verify if version is **older than 1.26.5**.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

✅ **Fix**: Upgrade to **version 1.26.5 or later**.
🔗 **Ref**: See GitHub Advisory GHSA-48f4-h726-74p5.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **Workaround**: If unpatched, **disable** the vulnerable macro or restrict network access to the XWiki instance immediately.

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Priority**: **CRITICAL (S1)**.
🏃 **Action**: Patch immediately. CVSS 9.8 + No Auth = High risk of automated exploitation.

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

CVE-2025-55728 — 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