dbcve.org
Moslistmessenger ComponentApplication · Joomla

CVE-2006-4229

HIGH · 7.5 CVSS v2.0 Published 2006-08-18
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 archive.php in the mosListMessenger Component (com_lm) before 20060719 for Mambo and Joomla! allows remote attackers to execute arbitrary PHP code via a URL in the mosConfig_absolute_path parameter.

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 confidence

This is a Remote File Inclusion (RFI) vulnerability in the mosListMessenger component for Mambo/Joomla. The archive.php file uses the mosConfig_absolute_path parameter to include files without proper validation, allowing attackers to inject and execute arbitrary PHP code by pointing the parameter to a malicious remote file.

MitigationUpgrade the com_lm component to version 20060719 or later. As an immediate workaround, disable the affected component or implement input validation to restrict the mosConfig_absolute_path parameter to trusted values.

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
Moslistmessenger ComponentApplication
Affected:all versions
Moslistmessenger 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 moslistmessenger component directory
    Search the web root for directories named 'com_moslistmessenger', 'com_lm', or 'moslistmessenger' - these are typical installation paths for the Moslistmessenger component in Mambo/Joomla installations
    Affected if The component directory exists on the server, indicating the vulnerable component is installed
  2. Verify archive.php exists in the component
    Check for the file archive.php within the component directory (for example: /components/com_moslistmessenger/archive.php or similar path)
    Affected if The archive.php file exists, which contains the vulnerable include logic using mosConfig_absolute_path
  3. Inspect archive.php for the RFI vulnerability
    Open archive.php and search for code patterns like 'include($mosConfig_absolute_path' or 'require($mosConfig_absolute_path' without proper validation or sanitization of the parameter
    Affected if The file contains an include/require statement using the mosConfig_absolute_path variable directly without validation, allowing arbitrary remote URLs to be injected
  4. Check PHP runtime configuration
    Review the PHP configuration settings allow_url_fopen and allow_url_include - check phpinfo() or the local php.ini file
    Affected if allow_url_fopen is enabled (default) or allow_url_include is enabled, which permits PHP to include remote files and enables the RFI attack vector
  5. Determine if the component is accessible via web
    Test accessing the archive.php file directly through the web server (e.g., curl or browser request to /components/com_moslistmessenger/archive.php)
    Affected if The file is web-accessible and responds, meaning an attacker could potentially exploit the RFI vulnerability over the network

If the moslistmessenger component is installed with archive.php present and that file contains an unprotected include using mosConfig_absolute_path, the environment is affected by this RFI vulnerability.

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

Upgrade the com_lm component to version 20060719 or later. As an immediate workaround, disable the affected component or implement input validation to restrict the mosConfig_absolute_path parameter to trusted values.

Fix this in Moslistmessenger Component Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-4229 — 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-4229 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