CVE-2005-2819
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 · uneditedDownFile 1.3 allows remote attackers to gain administrator privileges via a direct request to (1) update.php, (2) del.php, and (3) add_form.php.
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 confidenceDownFile 1.3 contains multiple PHP scripts (update.php, del.php, add_form.php) that lack proper function-level access control, allowing unauthenticated remote attackers to directly invoke administrative operations and escalate privileges to administrator level.
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.3CVSS 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 DownFile 1.3 installationSearch the web root for DownFile files or check for version information in any index, readme, or config files. Look for directory names containing 'downfile' or 'downfile13'.Affected if DownFile version 1.3 is present on the server.
-
Locate vulnerable PHP scriptsSearch the DownFile installation directory for the files update.php, del.php, and add_form.php. Check both the root and any subdirectories.Affected if Any of these three PHP scripts (update.php, del.php, add_form.php) exist in the DownFile installation.
-
Inspect update.php for access controlOpen update.php in a text editor and search for function calls related to authentication, session validation, or privilege checking (e.g., 'session_start', 'is_admin', 'check_auth', 'level'). Compare the script structure to see if these checks occur before administrative operations.Affected if The script contains no authentication or session validation before executing administrative actions.
-
Inspect del.php for access controlOpen del.php and examine whether it validates user identity or privilege level before allowing file deletion operations. Look for session checks, permission flags, or role verification.Affected if The script executes deletion commands without verifying user authentication or authorization.
-
Inspect add_form.php for access controlOpen add_form.php and determine whether it enforces any access restrictions before displaying or processing form submission. Check if guest/unauthenticated users can access administrative form functionality.Affected if The script is accessible to unauthenticated users and allows administrative operations without credentials.
You are affected if DownFile version 1.3 is installed and any of the scripts update.php, del.php, or add_form.php are present without proper authentication checks.
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 dataRestrict access to update.php, del.php, and add_form.php by implementing proper authentication and session-based authorization checks before executing administrative actions, or remove these files if the functionality is not required.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-2819 — 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-2819 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