dbcve.org
PhpwcmsApplication · Oliver Georgi

CVE-2006-7018

HIGH · 10.0 CVSS v2.0 Published 2007-02-15
Fix available
A fix is available. Upgrade to after 1.2.5_dev or later.
See remediation →
100/100
Remediation priority · Urgent
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
phpwcms 1.2.5-DEV and earlier, and 1.1 before RC4, allows remote attackers to execute arbitrary code via a crafted argument to the nome_evento parameter to phpwcms_code_snippets/mail_file_form.php and (2) sample_ext_php/mail_file_form.php, which is processed by the render_PHPcode function.

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

phpwcms versions 1.2.5-DEV and earlier, and 1.1 before RC4, contain a remote code execution vulnerability in the mail_file_form.php files within phpwcms_code_snippets and sample_ext_php directories. The nome_evento parameter is processed by the render_PHPcode function without sanitization, allowing injection of arbitrary PHP code.

MitigationUpgrade to a patched version of phpwcms (1.2.5-DEV or 1.1 RC4 and later). If upgrading is not feasible, remove or disable access to the vulnerable mail_file_form.php files and ensure PHP execution is disabled in these directories.

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
PhpwcmsApplication
Affected:<= 1.1_rc3<= 1.2.5_dev

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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Identify phpwcms installation and version
    Search for phpwcms by looking for index.php or config.php files in the web root. Check for a version file or inspect the header of main PHP files for version strings like 'phpwcms 1.2.5-DEV' or 'phpwcms 1.1 RC3' or earlier.
    Affected if The installed version is 1.2.5-DEV or earlier, or 1.1 RC3 or earlier.
  2. Locate vulnerable mail_file_form.php files
    Search the web document root for files named mail_file_form.php within phpwcms_code_snippets and sample_ext_php directories.
    Affected if These files exist in the expected directories.
  3. Check web accessibility of vulnerable directories
    Attempt HTTP access to the phpwcms_code_snippets and sample_ext_php directories via browser or curl to determine if they are web-accessible.
    Affected if The directories are accessible via HTTP without authentication.
  4. Inspect render_PHPcode function usage
    Examine the mail_file_form.php files and look for the render_PHPcode function being called with the nome_evento parameter without sanitization.
    Affected if The code processes the nome_evento parameter through render_PHPcode without input sanitization.
  5. Verify PHP execution is enabled
    Check the web server configuration and .htaccess files in the phpwcms_code_snippets and sample_ext_php directories for PHP execution settings.
    Affected if PHP execution is permitted in these directories (no php_flag engine off or equivalent restriction).

A user is affected if phpwcms version 1.2.5-DEV/1.2.5 or earlier, or 1.1 RC3 or earlier is installed with the mail_file_form.php files accessible and PHP execution enabled in the phpwcms_code_snippets or sample_ext_php directories.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.2.5_dev
Interim mitigation

Upgrade to a patched version of phpwcms (1.2.5-DEV or 1.1 RC4 and later). If upgrading is not feasible, remove or disable access to the vulnerable mail_file_form.php files and ensure PHP execution is disabled in these directories.

Recommended fix Moderate confidence

phpwcms 1.1.4 stable or 1.2.6+ (depending on your branch)

  1. 1. Identify the currently installed phpwcms version by checking the version file or admin interface
  2. 2. For phpwcms 1.1.x branch: Upgrade to phpwcms 1.1 RC4 or later (1.1.4 stable is recommended)
  3. 3. For phpwcms 1.2.x branch: Upgrade to phpwcms 1.2.6 or later stable release
  4. 4. After upgrade, verify that the files phpwcms_code_snippets/mail_file_form.php and sample_ext_php/mail_file_form.php have been updated or removed
  5. 5. Review the render_PHPcode function to ensure proper input sanitization if custom code is still present
  6. 6. Test that the mail_file_form functionality works correctly after the upgrade
  7. 7. Monitor phpwcms security advisories for any further updates
Caveat Minor - upgrading within same major version should not break functionality, but test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Phpwcms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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