CVE-2004-2669
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 · uneditedMultiple SQL injection vulnerabilities in Land Down Under (LDU) v701 allow remote attackers to execute arbitrary SQL commands or obtain the installation path via parameters including (1) s, w, and d in users.php, (2) id in comments.php, (3) rusername in auth.php, or (4) h in plug.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 confidenceLand Down Under (LDU) v701 contains multiple SQL injection vulnerabilities in four PHP files. Attackers can inject arbitrary SQL commands through the 's', 'w', and 'd' parameters in users.php, the 'id' parameter in comments.php, the 'rusername' parameter in auth.php, and the 'h' parameter in plug.php. These vulnerabilities stem from improper input sanitization allowing SQL meta-characters to be passed directly to database queries.
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= 701CVSS 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 Land Down Under is installedSearch the web root for LDU-specific files such as index.php, users.php, comments.php, auth.php, or plug.php. Look for references to 'Land Down Under' or 'LDU' in page footers or source code.Affected if The application is Neocrome Land Down Under
-
Verify the exact LDU versionCheck for a version file, readme, or CHANGELOG in the installation directory. Alternatively, view the source of any LDU page for a version comment or meta tag.Affected if The installed version is exactly 701 (v701)
-
Identify if vulnerable PHP files existCheck for the presence of users.php, comments.php, auth.php, and plug.php in the web-accessible directories, typically under /users.php, /comments.php, /auth.php, or /plug.php.Affected if Any of these four files exist in the installation
-
Confirm database connectivityVerify the application is configured with a MySQL database by checking for a config file containing database credentials or connection strings.Affected if The application connects to a MySQL database
-
Check if vulnerable parameters are processedReview the source code of the four affected files (users.php, comments.php, auth.php, plug.php) to confirm the parameters s, w, d, id, rusername, and h are used in SQL queries without apparent sanitization or parameterization.Affected if The vulnerable parameters are passed directly to SQL queries without sanitization
A user is affected if Land Down Under v701 is installed with the vulnerable PHP files present and connected to a database, where user-supplied input flows directly into SQL queries.
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 dataUpgrade to a patched version of LDU that addresses these SQL injection vulnerabilities. If no update exists, implement parameterized queries or prepared statements for all user-supplied input in the affected files, and add input validation/sanitization for the s, w, d, id, rusername, and h parameters.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-2669 — 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-2004-2669 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