Taskfreak\! Multi MysqlDatabase / datastore · Taskfreak

CVE-2011-3805

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
TaskFreak! multi-mysql-0.6 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 include/language/zh/register_info.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

TaskFreak! multi-mysql-0.6 contains PHP include files that can be directly requested by remote attackers, causing error messages that reveal the server's installation path. Files like include/language/zh/register_info.php and similar include files are vulnerable to this path disclosure.

MitigationRestrict direct web access to PHP include files by implementing proper front-controller patterns or access controls, and disable detailed PHP error messages in production environments to prevent information disclosure.

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
Taskfreak\! Multi MysqlDatabase / datastore
Affected:= 0.6

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. Identify TaskFreak version
    Locate the version file or check the main index page source for the version string 'TaskFreak! Multi MySQL 0.6'
    Affected if The installed version is exactly 0.6 (TaskFreak! Multi MySQL)
  2. Check for include directory access
    Verify the web server configuration allows direct access to the 'include/' directory and its subdirectories via HTTP
    Affected if The include/ directory is web-accessible without restrictions
  3. Test vulnerable PHP include file access
    Use a web browser or curl to request 'include/language/zh/register_info.php' directly and observe the response
    Affected if The request returns a PHP error message revealing the server's absolute file path
  4. Check for other vulnerable include files
    Attempt direct HTTP requests to other files in 'include/language/*/' directories (e.g., register_info.php, login.php)
    Affected if Any include file responds with path disclosure errors when accessed directly
  5. Verify PHP error display settings
    Check php.ini for 'display_errors = On' or inspect PHPINFO output
    Affected if PHP error messages are enabled and visible to web visitors

The environment is affected if TaskFreak! Multi MySQL version 0.6 is installed AND PHP include files in the include/ directory are directly web-accessible AND PHP error display is enabled, allowing path disclosure.

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

Restrict direct web access to PHP include files by implementing proper front-controller patterns or access controls, and disable detailed PHP error messages in production environments to prevent information disclosure.

Fix this in Taskfreak\! Multi Mysql Scoped from the published advisory
  • Consultation1.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,220
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-3805 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