CVE-2005-4861
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 · uneditedfunctions.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.
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 confidenceThe CHECK_AUTH function in functions.php of Ragnarok Online Control Panel (ROCP) 4.3.4a fails to properly sanitize the PHP_SELF server variable when it contains a trailing '/login.php' path. This allows remote attackers to bypass authentication checks by crafting requests to account_manage.php with a manipulated PHP_SELF value.
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= 4.3.4aCVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ROCP installation and versionLocate the control panel files and check for version identifier 4.3.4a in any version file, README, or installation manifestAffected if The installed version is exactly 4.3.4a
-
Locate functions.phpFind the functions.php file within the ROCP installation directoryAffected if functions.php exists in the ROCP web root or include directory
-
Examine CHECK_AUTH functionOpen functions.php and search for the CHECK_AUTH function definitionAffected if The CHECK_AUTH function exists and handles authentication logic
-
Inspect PHP_SELF handlingWithin CHECK_AUTH, look for code that uses $_SERVER['PHP_SELF'] and check if it properly sanitizes or validates the variable, especially for trailing '/login.php' stringsAffected if PHP_SELF is used without proper sanitization of path segments like '/login.php'
-
Verify affected endpoint existsCheck if account_manage.php exists in the ROCP installationAffected if account_manage.php is present and accessible
A user is affected if ROCP version 4.3.4a is installed with a vulnerable functions.php where CHECK_AUTH fails to sanitize PHP_SELF, allowing the authentication bypass to succeed.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply input sanitization to PHP_SELF in the CHECK_AUTH function to validate and reject unexpected path segments, or upgrade to a patched version if available. Consider migrating to a supported application as ROCP appears to be abandoned.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-4861 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-4861 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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