CVE-2005-4824
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 web/classes.php in Siteframe before 3.2.2 allows remote attackers to execute arbitrary PHP code via a URL in the LOCAL_PATH parameter, a different vulnerability than CVE-2005-1965.
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 Siteframe before version 3.2.2 allows remote attackers to execute arbitrary PHP code via the LOCAL_PATH parameter in web/classes.php. The vulnerable code includes external files based on user-controllable input without proper validation.
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<= 3.2.1CVSS 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.
-
Identify Siteframe versionLocate and examine the Siteframe version information (check version file, admin interface, or source headers) and compare it to the affected range: version 3.2.1 or earlierAffected if The installed version is 3.2.1 or any version prior to 3.2.2
-
Verify web/classes.php existsConfirm that the file web/classes.php exists in your Siteframe installation directory and is accessible via the web serverAffected if The file web/classes.php exists and is web-accessible
-
Test LOCAL_PATH parameter handlingReview the code in web/classes.php to determine if the LOCAL_PATH parameter is used in an include or require statement without proper validation, or test by supplying a remote URL value to the LOCAL_PATH parameter via HTTP requestAffected if The LOCAL_PATH parameter is used to include files based on user-supplied input without validation
-
Check PHP remote inclusion settingsExamine PHP configuration (php.ini) for the allow_url_fopen and allow_url_include directivesAffected if allow_url_fopen or allow_url_include is enabled (On) and the application code is vulnerable to LOCAL_PATH manipulation
You are affected if you are running Siteframe version 3.2.1 or earlier, the web/classes.php file is present and web-accessible, the LOCAL_PATH parameter can be controlled by users without validation, and PHP's allow_url_fopen or allow_url_include is enabled.
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 to Siteframe 3.2.2 or later to obtain the vendor patch. As a defensive measure, ensure PHP's allow_url_fopen and allow_url_include directives are disabled to prevent remote file inclusion attacks.
- 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-2005-4824 — 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-4824 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