CVE-2006-6975
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 centipaid_class.php in CentiPaid 1.4.3 allows remote attackers to execute arbitrary code via a URL in the class_pwd parameter. NOTE: this issue has been disputed by CVE and multiple third parties, who state that $class_pwd is set to a static value before the relevant include statement
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 confidencePHP remote file inclusion vulnerability in centipaid_class.php of CentiPaid 1.4.3 allows remote attackers to execute arbitrary code via a URL in the class_pwd parameter. NOTE: This vulnerability is disputed by CVE and third parties who state that $class_pwd is set to a static value before the relevant include statement, potentially mitigating the risk.
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.4.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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 centipaid_class.php in your web rootSearch your web server document root for the file centipaid_class.php using: find /var/www -name 'centipaid_class.php' 2>/dev/null (Linux) or dir /s C:\centipaid_class.php (Windows)Affected if The file exists and is accessible via web server
-
Identify the installed CentiPaid versionCheck any version file, README, or the header of centipaid_class.php for a version string; look for comments like 'CentiPaid v1.4.3' or check VERSION file in the application rootAffected if The installed version is exactly 1.4.3 (no other versions are listed as affected)
-
Verify if class_pwd is user-controllableOpen centipaid_class.php and locate the line 'include($class_pwd)' or similar. Immediately before this include, check if $class_pwd is assigned a hardcoded static value (e.g., $class_pwd = 'centipaid.php';) or if it receives input directly from $_GET, $_POST, or $_REQUEST without filteringAffected if $class_pwd is NOT hardcoded and accepts direct user input without validation - this confirms the vulnerability is present
-
Check PHP allow_url_include settingCreate a PHP file with '<?php echo ini_get("allow_url_include"); ?>' and access it via web browser, or check php.ini for 'allow_url_include = On'Affected if allow_url_include is enabled (On), which would allow remote URL inclusion if class_pwd is exploitable
You are affected only if centipaid_class.php exists, the version is exactly 1.4.3, AND the $class_pwd variable is NOT hardcoded before the include statement (making it user-controllable). The disputed status means many installations may not be vulnerable.
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 dataVerify whether $class_pwd is indeed hardcoded before use; if exploitable, disable allow_url_include in PHP configuration and implement strict input validation on the class_pwd parameter.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6975 — 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-2006-6975 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