CVE-2005-1047
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 · uneditedMeilad File upload script (up.php) mod for phpBB 2.0.x does not properly limit the types of files that can be uploaded, which allows remote authenticated users to execute arbitrary commands by uploading PHP files, then directly requesting them from the uploads directory.
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 confidenceThe Meiland File upload script (up.php) mod for phpBB 2.0.x fails to validate file types during upload, allowing authenticated users to upload arbitrary PHP files. When these files are accessed directly via the web server, they execute, enabling remote command execution on the host.
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= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.6c= 2.0.6d= 2.0.7= 2.0.7a= 2.0.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm phpBB 2.0.x installationLocate the phpBB installation directory and check for the existence of the main configuration file (config.php) and version file (common.php). Examine common.php or a version file for the $phpbb_version variable to confirm the installed version falls within 2.0.0 to 2.0.8.Affected if phpBB version 2.0.0 through 2.0.8 is confirmed to be installed
-
Identify Meiland up.php upload mod presenceSearch the phpBB root directory and subdirectories for a file named up.php, which is the Meiland file upload script. Common paths include the root directory or a mods subdirectory. Check file headers for the Meiland mod signature.Affected if The up.php file from the Meiland upload mod exists in the phpBB installation
-
Verify uploads directory is web-accessibleCheck the configuration of the uploads directory as referenced in up.php. Determine if this directory is located within the web document root (htdocs, www, public_html). Attempt a direct HTTP request to the uploads directory to confirm it is accessible via the web server.Affected if The uploads folder is accessible via HTTP requests from the web server
-
Confirm script execution is allowed in uploads directoryExamine the .htaccess file in the uploads directory (if it exists) or the web server configuration. Look for directives that allow or restrict PHP script execution (such as php_flag engine off or RemoveHandler .php). Check if the server configuration permits PHP execution in that directory.Affected if PHP files in the uploads directory can be executed when requested directly via HTTP
A user is affected if they have phpBB 2.0.x with the Meiland up.php mod installed, the uploads directory is web-accessible, and PHP execution is permitted in that directory, allowing arbitrary PHP file upload and remote code execution.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict allowlist-based file type validation (extension and MIME type), store uploaded files outside the web root or disable script execution via .htaccess/php.ini, and ensure uploaded files cannot be directly requested from the uploads directory.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-1047 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-1047 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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