# CVE-2005-4861: Auth bypass in n/a

> Remote attackers can bypass authentication in Ragnarok Online Control Panel by manipulating the PHP_SELF value, gaining unauthorized access to account management features.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2007
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-96xp-3qc9-8xh8

## What is CVE-2005-4861?

CVE-2005-4861 is a high-severity authentication bypass vulnerability in n/a, published on 5 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

functions.php in Ragnarok Online Control Panel (ROCP) 4.3.4a allows remote attackers to bypass authentication by requesting account_manage.php with a trailing "/login.php" PHP_SELF value, which is not properly handled by the CHECK_AUTH function.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2005-4861?

It affects 1 product.


Products: Jasio.net Ragnarok Online Control Panel.

## How do I fix CVE-2005-4861?

No fix has been published for CVE-2005-4861 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-4861 being exploited?

There is no known exploitation of CVE-2005-4861 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4861 and fix it if it is affected.

What it is: CVE-2005-4861 is a high-severity authentication bypass vulnerability in n/a, published on 5 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4861 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2005-4861/ (Markdown: https://insights.sbomify.com/CVE-2005-4861/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-4861
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-4861
- OSV: https://osv.dev/vulnerability/CVE-2005-4861

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-4861/
Summaries are generated and may contain mistakes; the official description above is the record.