CVE-2007-2024
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 · uneditedUnrestricted file upload vulnerability in the UpLoad feature (lib/plugin/UpLoad.php) in PhpWiki 1.3.x allows remote attackers to upload arbitrary PHP files with a (1) php3, (2) php4, or (3) php5 extension.
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 UpLoad feature in PhpWiki 1.3.x (lib/plugin/UpLoad.php) lacks proper file type validation, allowing remote attackers to upload executable PHP files with .php3, .php4, or .php5 extensions. These uploaded files can then be accessed and executed on the server, potentially leading to remote code execution.
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= 1.3.xCVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 PhpWiki installationLocate the PhpWiki installation directory on the server by checking web server document roots or known deployment paths. Look for the presence of PhpWiki files such as index.php, config.php, or the lib/ directory.Affected if PhpWiki is installed and accessible via the web server
-
Identify the installed PhpWiki versionExamine the version file or source code within the PhpWiki installation directory. Common version indicators may be in a VERSION file, in the main index.php, or in a file named about.php or similar. Compare the discovered version against the 1.3.x branch.Affected if The installed version falls within the 1.3.x branch
-
Locate the UpLoad plugin fileVerify the existence of the file lib/plugin/UpLoad.php within the PhpWiki installation directory. This file contains the vulnerable upload functionality.Affected if The file lib/plugin/UpLoad.php exists on the system
-
Determine if the UpLoad feature is enabledCheck PhpWiki configuration files (typically config.php or a similar configuration file in the root directory) for settings related to the UpLoad plugin. Look for parameters like ENABLE_UPLOAD, ALLOW_UPLOAD, or plugin inclusions that enable the upload functionality.Affected if The UpLoad feature is enabled in the configuration, allowing users to upload files
-
Inspect upload file type restrictionsReview the upload configuration and the UpLoad.php source code to determine what file extensions are allowed. Look for any validation logic that restricts file types, specifically checking whether PHP-related extensions (.php, .php3, .php4, .php5) are blocked.Affected if File type validation is absent or permits PHP-related extensions (.php3, .php4, .php5) for upload
A user is affected if they are running PhpWiki 1.3.x with the UpLoad feature enabled and without proper file type validation that blocks PHP extensions.
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 dataDisable the UpLoad feature in PhpWiki or implement strict file type validation that rejects PHP file extensions and only allows safe, non-executable file types for upload.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2024 — 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-2007-2024 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