dbcve.org
Contacts Xtd ComponentApplication · Mambo

CVE-2006-4375

HIGH · 7.5 CVSS v2.0 Published 2006-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
PHP remote file inclusion vulnerability in contxtd.class.php in the Contacts XTD (ContXTD) component for Mambo (com_contxtd) allows remote attackers to execute arbitrary PHP code via a URL in the mosConfig_absolute_path parameter. NOTE: another researcher has disputed this issue, saying that the software prevents the attack by checking whether _VALID_MOS is defined

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 confidence

PHP Remote File Inclusion (RFI) vulnerability in contxtd.class.php of the ContXTD Mambo component allows attackers to inject arbitrary PHP code via the mosConfig_absolute_path parameter. The vulnerability stems from unsanitized user input being used in a require/include statement. However, a researcher disputes the exploitability, claiming the code checks for _VALID_MOS defined, which may block the attack.

MitigationIf the component is still in use, remove or disable the vulnerable com_contxtd component entirely, or apply any available vendor patch. Verify whether _VALID_MOS check exists in the file and add proper input validation/constant checks if missing. Consider migrating to a maintained alternative.

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
Contacts Xtd ComponentApplication
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the ContXTD component installation
    Search the Mambo/Joomla installation for the 'com_contxtd' component directory, typically found in /administrator/components/com_contxtd/ or /components/com_contxtd/. Also check for the vulnerable file contxtd.class.php anywhere in the webroot.
    Affected if The com_contxtd component directory exists on the server, indicating the vulnerable component is installed.
  2. Verify the vulnerable file exists and examine _VALID_MOS check
    Open contxtd.class.php and search for '_VALID_MOS' constant definition near the top of the file. Determine whether the code checks for this constant before processing include/require statements.
    Affected if The contxtd.class.php file exists and the _VALID_MOS check is missing or improperly implemented, meaning the RFI protection is not active.
  3. Identify the insecure require/include pattern
    Search the file for 'require' or 'include' statements that use 'mosConfig_absolute_path' as part of the path. Look for patterns like require($mosConfig_absolute_path . '/...') where the parameter is not sanitized or validated.
    Affected if The code contains require/include statements using mosConfig_absolute_path without proper sanitization, and _VALID_MOS is not checked or is bypassed.
  4. Check if the mosConfig_absolute_path parameter is user-controllable
    Determine whether the mosConfig_absolute_path value can be controlled via URL parameters (GET/POST) or other user input. Review how this configuration variable is set in the Mambo application context.
    Affected if The mosConfig_absolute_path parameter can be influenced through user input without validation, combined with the missing _VALID_MOS check, making exploitation possible.

You are affected if the ContXTD component is installed, contxtd.class.php exists, and the _VALID_MOS constant check is either missing or can be bypassed, allowing the mosConfig_absolute_path parameter to be controlled in require/include statements.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If the component is still in use, remove or disable the vulnerable com_contxtd component entirely, or apply any available vendor patch. Verify whether _VALID_MOS check exists in the file and add proper input validation/constant checks if missing. Consider migrating to a maintained alternative.

Fix this in Contacts Xtd Component Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-4375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-4375 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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