CVE-2006-6748
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 i-accueil.php in Newxooper 0.9 and earlier allows remote attackers to execute arbitrary PHP code via a URL in the chemin parameter. 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 confidenceRemote file inclusion vulnerability in i-accueil.php of Newxooper 0.9 and earlier allows arbitrary PHP code execution via the 'chemin' parameter, which accepts a URL to a remote malicious PHP 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<= 0.9CVSS 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 Newxooper installation and versionCheck your web server for the Newxooper application directory. Look for version information in any version file, readme, or within the application's source code (often in a config file or main index file). Compare the found version to '<= 0.9'.Affected if Newxooper version 0.9 or earlier is installed.
-
Locate the vulnerable i-accueil.php fileSearch the web root directory for the file i-accueil.php. This is typically found in the main Newxooper directory or a subdirectory. Use 'find' or file browser to locate it.Affected if The file i-accueil.php exists in the Newxooper installation directory.
-
Verify the 'chemin' parameter is acceptedInspect the source code of i-accueil.php. Look for code that reads the 'chemin' parameter (e.g., via $_GET, $_REQUEST) and passes it to include(), require(), or similar functions without sanitization.Affected if The file contains code that uses the 'chemin' parameter in an include/require statement without validation.
-
Confirm web accessibilityAttempt to access i-accueil.php via HTTP/HTTPS through your web browser or curl command (e.g., curl http://yourdomain/path/i-accueil.php). Verify the web server serves the file.Affected if The vulnerable file is accessible over the web (not blocked by .htaccess, authentication, or removed from web-accessible directory).
You are affected if Newxooper version 0.9 or earlier is installed, the i-accueil.php file exists and is web-accessible, and the 'chemin' parameter is used in an unsafe include/require statement.
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 dataRemove or delete the vulnerable i-accueil.php file if not required, or upgrade to a patched version of Newxooper if available. Implement strict input validation on the 'chemin' parameter to disallow URL inputs if the functionality is needed.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6748 — 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-6748 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