dbcve.org
RathenaApplication

CVE-2025-58448

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 2025-09-06 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
rAthena is an open-source cross-platform massively multiplayer online role playing game (MMORPG) server. Versions prior to commit 0d89ae0 have a SQL Injection in the PartyBooking component via `WorldName` parameter. Commit 0d89ae0 fixes the issue.

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 confidence

SQL injection vulnerability in the PartyBooking component of the rAthena MMORPG server via the WorldName parameter, allowing remote attackers to execute arbitrary SQL commands. Fixed in commit 0d89ae0.

MitigationUpgrade rAthena to commit 0d89ae0 or later to patch the SQL injection vulnerability in the PartyBooking component.

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
RathenaApplication
Affected:< 2025-09-06

CVSS 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify rAthena server is running
    Check for rAthena server processes (e.g., look for 'athena' or 'rAthena' processes using task manager or commands like 'ps aux | grep athena' on Linux)
    Affected if rAthena server software is present and running on the system
  2. Determine rAthena version
    Use the server's version display command (common options: -v, --version, or check a version file in the server directory). Compare the installed version date or commit hash to the fixed state (2025-09-06 or commit 0d89ae0)
    Affected if The installed version is dated before 2025-09-06 or the commit hash is earlier than 0d89ae0
  3. Confirm PartyBooking component is enabled
    Inspect the rAthena configuration files (commonly found in the conf/ or config/ directory) for PartyBooking-related settings. Look for a boolean flag or setting like 'party_booking' or 'partybooking' set to enabled or true
    Affected if PartyBooking is enabled in the server configuration
  4. Check if WorldName parameter is exposed
    Identify if the PartyBooking HTTP/API endpoint is accessible by reviewing network configuration or attempting a request to the party booking interface (if known). A basic test: if the server accepts party booking requests over the network, the vulnerable parameter may be reachable
    Affected if The PartyBooking feature is network-accessible and accepts the WorldName parameter

If rAthena is running with PartyBooking enabled and the version predates the 2025-09-06 patch (commit 0d89ae0), the environment is vulnerable to SQL injection via the WorldName parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2025-09-06 or later
Fixed in 2025-09-06
Vendor patch github.com →
Interim mitigation

Upgrade rAthena to commit 0d89ae0 or later to patch the SQL injection vulnerability in the PartyBooking component.

Recommended fix High confidence

Checkout/pull commit 0d89ae071ff5e46e8dedcf45d060acec84b3abb5 or later (2025-09-06 release or newer)

  1. Navigate to the rAthena repository directory
  2. Fetch the latest changes from the remote repository: git fetch origin
  3. Apply the specific fix commit: git cherry-pick 0d89ae071ff5e46e8dedcf45d060acec84b3abb5 OR checkout to the commit: git checkout 0d89ae071ff5e46e8dedcf45d060acec84b3abb5
  4. Rebuild the server application after applying the patch
  5. Restart the rAthena server service to load the patched code
  6. Verify the PartyBooking component no longer accepts unsanitized WorldName parameter input

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rathena Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58448 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58448 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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