CVE-2009-0517
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 · uneditedEval injection vulnerability in index.php in phpSlash 0.8.1.1 and earlier allows remote attackers to execute arbitrary PHP code via the fields parameter, which is supplied to an eval function call within the generic function in include/class/tz_env.class. NOTE: some of these details are obtained from third party information.
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 confidenceCVE-2009-0517 is an eval injection vulnerability in phpSlash 0.8.1.1 and earlier, allowing remote attackers to execute arbitrary PHP code via the fields parameter in the index.php file. This occurs due to improper handling of input in the generic function within include/class/tz_env.class.
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 dataall versions<= 0.8.1.1= 0.5.3.2= 0.6= 0.6.1= 0.6.2= 0.7.1= 0.7.2= 0.8.0= 0.8.1= 0.61= 065CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 phpSlash installationLocate the phpSlash installation by checking for index.php in the web root directory. Look for the presence of the 'index.php' file and the 'include/class/' directory structure typical of phpSlash.Affected if phpSlash is installed and accessible via the web server.
-
Identify phpSlash versionSearch for version information in the phpSlash installation. Check common version files like VERSION, version.php, or look for version strings within the main index.php or configuration files.Affected if The installed version matches any of the affected versions: 0.8.1.1 and earlier, or specifically 0.5.3.2, 0.6, 0.6.1, 0.6.2, 0.7.1, 0.7.2, 0.8.0, 0.8.1, 0.61, or 065.
-
Verify vulnerable file existsCheck for the presence of the file 'include/class/tz_env.class' within the phpSlash installation directory.Affected if The file include/class/tz_env.class exists in the installation.
-
Inspect vulnerable functionExamine the include/class/tz_env.class file and locate the 'generic' function. Look for any usage of eval() that processes the 'fields' parameter without proper sanitization.Affected if The generic function in tz_env.class contains eval() calls that process the fields parameter from user input.
-
Test parameter accessibilityReview the index.php file to confirm that user-supplied 'fields' parameter can be passed to the vulnerable function in tz_env.class. This may require checking how index.php includes and calls the generic function.Affected if The fields parameter from HTTP requests is passed directly to the eval-containing function without input validation.
A system is affected if phpSlash is installed with a version at or below 0.8.1.1, the vulnerable tz_env.class file exists with the eval-capable generic function, and the fields parameter is accessible to untrusted 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 dataTo remediate this vulnerability, it is essential to upgrade to a patched version of phpSlash that addresses the eval injection issue. Additionally, input validation and sanitization should be implemented to prevent similar vulnerabilities.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0517 — 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-2009-0517 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