CVE-2005-3571
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 file inclusion vulnerability in protection.php in CodeGrrl (a) PHPCalendar 1.0, (b) PHPClique 1.0, (c) PHPCurrently 2.0, (d) PHPFanBase 2.1, and (e) PHPQuotes 1.0 allows remote attackers to include arbitrary local files via the siteurl parameter when register_globals is enabled. NOTE: It was later reported that PHPFanBase 2.2 is also affected.
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 confidenceLocal file inclusion vulnerability in protection.php allows remote attackers to include arbitrary local files via the siteurl parameter. When register_globals is enabled (a deprecated and dangerous PHP setting), attacker-controlled input is used in PHP include/require statements without validation, enabling disclosure of sensitive local files or potentially 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<= 1.0<= 1.0<= 2.0<= 2.2<= 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 installed Codegrrl productsSearch the web root for directories or files containing 'phpcalendar', 'phpclique', 'phpcurrently', 'phpfanbase', or 'phpquotes'. Check for protection.php in those directories.Affected if Any of the affected Codegrrl products (Phpcalendar <=1.0, Phpclique <=1.0, Phpcurrently <=2.0, Phpfanbase <=2.2, or Phpquotes <=1.0) are installed on the server.
-
Locate vulnerable protection.php fileFind protection.php in the installed Codegrrl product directories and verify it handles a 'siteurl' parameter.Affected if The protection.php file exists and processes the siteurl parameter in include/require statements without validation.
-
Check PHP register_globals settingRun 'php -i' or create a PHP script with 'phpinfo();' to check if register_globals is set to On, or check the php.ini configuration file.Affected if register_globals is enabled (On) in PHP configuration - this is the critical condition that enables the vulnerability.
-
Verify siteurl parameter handlingInspect protection.php source code to confirm that the siteurl parameter is directly used in include/require statements without input sanitization or validation.Affected if The siteurl parameter from GET/POST is used directly in include/require without filtering.
The environment is affected if any Codegrrl product (Phpcalendar, Phpclique, Phpcurrently, Phpfanbase, or Phpquotes) is installed with its protection.php file present AND register_globals is enabled in PHP configuration.
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 dataDisable register_globals in php.ini and add strict input validation/sanitization to the siteurl parameter in protection.php to ensure only expected values are accepted. Also disable allow_url_include to prevent remote file inclusion attacks.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3571 — 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-3571 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