dbcve.org
PhpwcmsApplication

CVE-2011-3789

MEDIUM · 5.0 CVSS v2.0 Published 2011-09-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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.4.7 r412 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by template/inc_script/frontend_render/disabled/majonavi.php and certain other files.

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

phpwcms 1.4.7 r412 contains multiple PHP files in the template/inc_script/frontend_render/disabled/ directory that, when accessed directly, expose the web server's installation path in PHP error messages. This path disclosure can aid attackers in reconnaissance for further attacks.

MitigationRemove or properly secure the disabled script files in template/inc_script/frontend_render/disabled/ directory, and configure PHP error handling to prevent path disclosure in production environments.

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.4.7

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
None
Availability
None

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

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 phpwcms installation and version
    Check for the presence of phpwcms by looking for its characteristic files (e.g., include/config/conf.inc.php or similar) and identify the version from version files or headers. Compare your installed version to the affected range (1.4.7 r412).
    Affected if The installed version is exactly 1.4.7 r412 or falls within the affected version range.
  2. Locate the disabled scripts directory
    Search for the directory template/inc_script/frontend_render/disabled/ within the phpwcms web root. This directory is intended to contain disabled or deprecated script files.
    Affected if The directory template/inc_script/frontend_render/disabled/ exists in the phpwcms installation.
  3. Check for PHP files in the disabled directory
    List the contents of the disabled directory to identify any PHP files present. These files, when accessed directly, may trigger PHP errors that disclose the installation path.
    Affected if PHP files exist in the disabled directory and are accessible via the web server.
  4. Test direct access to disabled PHP files
    Attempt to access one or more of the PHP files in the disabled directory directly through a web browser (e.g., http://yourdomain.com/template/inc_script/frontend_render/disabled/somefile.php). Observe if PHP error messages reveal the server's file system path.
    Affected if Direct web access to any disabled PHP file produces an error message that discloses the full server path (e.g., /var/www/html or C:\inetpub\).
  5. Check PHP error reporting configuration
    Review the PHP configuration (php.ini) or application-level error handling settings to determine if error display is enabled (display_errors=On) or if errors are being logged publicly.
    Affected if PHP display_errors is enabled or error output is visible in HTTP responses, allowing path information to be exposed.

A user is affected if they are running phpwcms version 1.4.7 r412 with the disabled directory and its PHP files accessible via the web, and PHP error reporting is configured to display errors publicly.

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

Remove or properly secure the disabled script files in template/inc_script/frontend_render/disabled/ directory, and configure PHP error handling to prevent path disclosure in production environments.

Fix this in Phpwcms 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-2011-3789 — 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-2011-3789 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