CVE-2025-58448 — AI Deep Analysis Summary

Q: Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-89** (SQL Injection). 🔍 **Flaw**: The `WorldName` parameter is not properly sanitized before being used in database queries. This allows malicious input to alter the query logic.

Q: Who is affected? (Versions/Components)

👥 **Affected**: Users running **rAthena** versions **prior to commit 0d89ae0**. 📦 **Component**: The core server software handling world name parameters.

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

⚡ **Exploitation Threshold**: **LOW**. 🌐 **Auth**: None required (`PR:N`). 🖱️ **UI**: None required (`UI:N`). 📡 **Access**: Network (`AV:N`). 🎯 **Complexity**: Low (`AC:L`). Easy to exploit remotely.

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

🔍 **Self-Check**: 1️⃣ Check your rAthena git commit hash. 2️⃣ If it is **older than 0d89ae0**, you are vulnerable. 3️⃣ Scan for SQL injection patterns in `WorldName` handling in your source code.

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

✅ **Fixed**: **YES**. 🔧 **Patch**: Commit **0d89ae071ff5e46e8dedcf45d060acec84b3abb5** fixes the issue. 🔗 **Ref**: [GitHub Advisory](https://github.com/rathena/rathena/security/advisories/GHSA-x99j-36m7-4vv7).

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **CRITICAL**. 📅 **Priority**: Patch **IMMEDIATELY**. ⚠️ **Reason**: Remote, unauthenticated, high-impact SQL injection. CVSS score indicates severe confidentiality and integrity loss.

Updated May 06, 2026 CVSS 9.1 · Critical

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: rAthena (MMORPG server) has a critical **SQL Injection** flaw.…

Read full answer (login)

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-89** (SQL Injection). <br>🔍 **Flaw**: The `WorldName` parameter is not properly sanitized before being used in database queries. This allows malicious input to alter the query logic.

Q3Who is affected? (Versions/Components)

👥 **Affected**: Users running **rAthena** versions **prior to commit 0d89ae0**. <br>📦 **Component**: The core server software handling world name parameters.

Q4What can hackers do? (Privileges/Data)

💀 **Hacker Capabilities**: <br>1️⃣ **Read**: Extract sensitive user data, passwords, and game logs. <br>2️⃣ **Write**: Modify game data or inject malicious content.…

Read full answer (login)

Q5Is exploitation threshold high? (Auth/Config)

⚡ **Exploitation Threshold**: **LOW**. <br>🌐 **Auth**: None required (`PR:N`). <br>🖱️ **UI**: None required (`UI:N`). <br>📡 **Access**: Network (`AV:N`). <br>🎯 **Complexity**: Low (`AC:L`). Easy to exploit remotely.

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

📜 **Public Exploit**: **No specific PoC code** listed in the data (`pocs: []`). <br>⚠️ **Reality**: SQL injection is a well-understood technique.…

Read full answer (login)

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: <br>1️⃣ Check your rAthena git commit hash. <br>2️⃣ If it is **older than 0d89ae0**, you are vulnerable. <br>3️⃣ Scan for SQL injection patterns in `WorldName` handling in your source code.

Q8Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: **YES**. <br>🔧 **Patch**: Commit **0d89ae071ff5e46e8dedcf45d060acec84b3abb5** fixes the issue. <br>🔗 **Ref**: [GitHub Advisory](https://github.com/rathena/rathena/security/advisories/GHSA-x99j-36m7-4vv7).

Q9What if no patch? (Workaround)

🚧 **No Patch Workaround**: <br>1️⃣ **Update** to the latest version immediately. <br>2️⃣ If updating is impossible, **sanitize** the `WorldName` input manually in the source code.…

Read full answer (login)

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **CRITICAL**. <br>📅 **Priority**: Patch **IMMEDIATELY**. <br>⚠️ **Reason**: Remote, unauthenticated, high-impact SQL injection. CVSS score indicates severe confidentiality and integrity loss.

Continue exploring

Vulnerability detail Full AI analysis (login) rathena CWE-89