CVE-2007-2254
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 · uneditedPHP remote file inclusion vulnerability in admin/setup/level2.php in PHP Classifieds 6.04, and probably earlier versions, allows remote attackers to execute arbitrary PHP code via a URL in the dir parameter. NOTE: this product was referred to as "Allfaclassfieds" in the original disclosure.
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 confidenceRemote file inclusion vulnerability in admin/setup/level2.php allows attackers to supply a URL via the 'dir' parameter, which is then directly included and executed as PHP code, enabling arbitrary remote 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= 6.04CVSS 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 Deltascripts Php Classifieds installationSearch the webroot for phpclassifieds-related files or directories. Typical paths include /phpclassifieds/, /classifieds/, or root-level PHP files with 'classifieds' naming. Look for index.php with Deltascripts branding or version strings.Affected if The application is not present on the server.
-
Identify installed versionExamine version files (version.php, version.txt), CHANGELOG files, or the main index/header file for a '6.04' version string. Check footer includes for version metadata.Affected if The version is 6.04 exactly.
-
Locate vulnerable fileCheck if admin/setup/level2.php exists in the webroot. Attempt to access it directly via HTTP (e.g., GET /admin/setup/level2.php).Affected if The file exists and is accessible via web request.
-
Verify vulnerable parameter usageInspect the source code of admin/setup/level2.php. Search for 'include' or 'require' statements using the 'dir' parameter without validation (e.g., include($_GET['dir']). Look for unsanitized dynamic inclusion.Affected if The code contains an unprotected include/require using the 'dir' parameter from user input.
-
Check application accessibilityVerify the admin/setup/ directory is publicly accessible (not blocked by .htaccess, authentication, or IP restrictions). Attempt a test request with a harmless dir value to confirm the parameter is processed.Affected if The vulnerable endpoint is exposed without authentication or restriction.
A user is affected if Deltascripts Php Classifieds version 6.04 is installed with the admin/setup/level2.php file accessible and containing unsanitized dynamic inclusion of the 'dir' parameter.
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 dataReplace dynamic file inclusion with a whitelist approach, validate the dir parameter against allowed values, or remove the vulnerable include statement entirely. If the application is outdated, consider migrating to a supported solution.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2254 — 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-2007-2254 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