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

🩹 **Fix Status**: **Yes**. • **Patch**: Upgrade to version **1.11.0** or later. • **Commit**: Fix confirmed in `c54aaeb` on GitHub.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. • CVSS Score indicates High Impact. • Easy to exploit (Low Complexity). • **Action**: Patch immediately if processing user-uploaded Word documents.

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: Mammoth (Word-to-HTML tool) has a critical flaw in handling `.docx` files.
💥 **Consequences**: Attackers can trigger **Directory Traversal** (CWE-22) or cause **Resource Exhaustion** (DoS).…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: **Missing Input Validation**. Specifically, the tool fails to verify file paths or types when processing documents.
🔍 **CWE**: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory).

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Affected Versions**:
• `mammoth` **0.3.25**
• All versions **before 1.11.0**
👤 **Developer**: Michael Williamson (Personal Project).

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

🕵️ **Attacker Capabilities**:
• **Read**: Access sensitive files outside the intended directory via traversal.
• **Disrupt**: Crash the service via resource overconsumption.…

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

⚠️ **Exploitation Threshold**: **Low**.
• **Network**: Remote (AV:N).
• **Auth**: None required (PR:N).
• **User Interaction**: Required (UI:R) - Victim must open/submit a malicious docx.

Question 6

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

Accepted Answer

📢 **Public Exploit**: **No**. The `pocs` field is empty.
🔗 **References**: Proof-of-concept links exist on GitHub/Snyk, but no automated wild exploitation tools are confirmed in the data.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**:
1. Scan your dependency tree for `mammoth` version < 1.11.0.
2. Check if your app processes untrusted `.docx` files using this library.
3. Look for file path manipulation in logs.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

🩹 **Fix Status**: **Yes**.
• **Patch**: Upgrade to version **1.11.0** or later.
• **Commit**: Fix confirmed in `c54aaeb` on GitHub.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch Workaround**:
• **Sanitize Inputs**: Validate all file paths and extensions strictly before passing to Mammoth.…

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **HIGH**.
• CVSS Score indicates High Impact.
• Easy to exploit (Low Complexity).
• **Action**: Patch immediately if processing user-uploaded Word documents.

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

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