CVE-2009-0610
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 · uneditedMultiple static code injection vulnerabilities in post.php in Simple PHP News 1.0 final allow remote attackers to inject arbitrary PHP code into news.txt via the (1) title or (2) date parameter, and then execute the code via a direct request to display.php. NOTE: the provenance of this information is unknown; the details are obtained solely 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 · moderate confidenceThis is a static code injection vulnerability in Simple PHP News 1.0 where unsanitized user input from the title or date parameters in post.php is written directly to news.txt, allowing arbitrary PHP code execution when display.php includes that file.
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.0CVSS 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.
-
Locate Simple PHP News installationSearch the web root for files named post.php, display.php, or news.txt, or look for a directory containing Simple PHP News. Check for the presence of a file named news.txt in a data or similar directory.Affected if The files post.php, display.php, and news.txt from Simple PHP News version 1.0 are present on the system
-
Verify the product versionOpen post.php and check for a version comment or identifier at the top of the file. Compare the installed version to the affected version 1.0.Affected if The installed version is Simple PHP News 1.0
-
Confirm the data directory is writableCheck file permissions on the directory containing news.txt (typically a data directory). On Linux, run: ls -la /path/to/data/directory. Verify the web server user has write permissions.Affected if The directory containing news.txt has write permissions for the web server user
-
Check if PHP execution is enabled in the data directoryReview the web server configuration (Apache .htaccess or nginx config) and any .htaccess file in the data directory. Look for directives like 'php_flag engine on' or missing restrictions on PHP execution.Affected if PHP execution is not disabled in the directory containing news.txt (no appropriate restrictions found)
-
Inspect news.txt for injected codeOpen news.txt in a text editor or use: cat /path/to/news.txt. Look for PHP code patterns such as '<?php', '<?=', or suspicious encoded content.Affected if news.txt contains PHP code delimiters (<?php, <?) or appears to contain injected malicious content
The environment is affected if Simple PHP News 1.0 is installed with post.php, display.php, and news.txt present, the data directory is writable by the web server, and PHP execution is allowed in that directory.
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 dataImplement strict input validation and sanitization (e.g., escaping or removing PHP delimiters) before writing user input to news.txt, and disable PHP execution in the data directory.
- 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-0610 — 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-0610 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