CVE-2009-2353
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 · uneditedencoder.php in eAccelerator allows remote attackers to execute arbitrary code by copying a local executable file to a location under the web root via the -o option, and then making a direct request to this file, related to upload of image files.
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 · moderate confidenceThe encoder.php script in eAccelerator contains a vulnerability in its file handling functionality where the -o option allows copying local executable files to locations under the web root. Attackers can copy existing local executables to web-accessible directories and then execute them via direct HTTP requests, achieving arbitrary code execution.
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= 0.9.4= 0.9.5= 0.9.5.1= 0.9.5.2= 0.9.5.3CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Identify if eAccelerator PHP extension is installedRun 'php -m' or 'php -i | grep eAccelerator' to list loaded PHP modules, or check phpinfo() output for the eAccelerator sectionAffected if eAccelerator appears in the loaded modules list
-
Determine installed eAccelerator versionCheck the eAccelerator version string from phpinfo() output, the 'php -i' command, or the extension file metadataAffected if The version matches 0.9.4, 0.9.5, 0.9.5.1, 0.9.5.2, or 0.9.5.3
-
Locate encoder.php script in the web document rootSearch for encoder.php in web-accessible directories, typically under /, /control, /encoder, or the eAccelerator installation directory; check common paths like /var/www/html/encoder.php or examine eAccelerator source distribution for this fileAffected if encoder.php exists and is web-accessible
-
Verify encoder.php is executable and accepts the -o parameterIf encoder.php is found, attempt a local test call (e.g., 'php encoder.php -o /tmp/test_output.php /etc/hosts' from command line) to confirm the file copy functionality worksAffected if The -o option successfully copies files to arbitrary locations, indicating the vulnerability is present
You are affected if eAccelerator versions 0.9.4 through 0.9.5.3 are installed AND the encoder.php script with the -o file copy functionality is accessible on the system.
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 dataRestrict or disable the encoder.php functionality, ensure web directories have no script execution permissions for uploaded files, and implement proper access controls on file operation functions.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-2353 — 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-2353 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