CVE-2005-4424
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 · uneditedDirectory traversal vulnerability in PHPKIT 1.6.1 R2 and earlier might allow remote authenticated users to execute arbitrary PHP code via a .. (dot dot) in the path parameter and a %00 at the end of the filename, as demonstrated by an avatar filename ending with .png%00.
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 confidenceDirectory traversal vulnerability in PHPKIT 1.6.1 R2 and earlier allows authenticated remote users to execute arbitrary PHP code by using .. (dot dot) sequences in the path parameter combined with a null byte (%00) truncation to bypass file extension validation, enabling upload of malicious PHP files disguised as image files.
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= 1.6.1= 1.6.02= 1.6.03CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/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 PHPKIT installation and versionLocate the PHPKIT installation and identify the version number. Common indicators include a version.php file, admin panel version display, or version strings in source files.Affected if The installed version is 1.6.1, 1.6.02, 1.6.03, or any version earlier than 1.6.1 R2.
-
Verify file upload functionality is enabledCheck if PHPKIT file upload feature is configured and accessible. This typically involves the profile or avatar upload functionality.Affected if File upload capability is enabled and accessible to authenticated users.
-
Check authentication mechanismDetermine whether user registration and authentication are enabled, allowing remote users to obtain valid credentials.Affected if The system allows creation of user accounts or authenticated access is possible.
-
Inspect upload handling codeExamine the PHPKIT source code responsible for handling file uploads, specifically looking for path parameter handling and file extension validation logic.Affected if The upload handler uses the 'path' parameter and performs extension validation that could be bypassed with null byte truncation.
You are affected if PHPKIT version 1.6.1, 1.6.02, 1.6.03, or earlier than 1.6.1 R2 is installed AND file upload functionality is enabled for authenticated users.
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 dataUpgrade PHPKIT to a version beyond 1.6.1 R2 that addresses this vulnerability, or implement robust input validation to strip .. sequences and null byte characters from file upload parameters.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-4424 — 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-4424 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