CVE-2004-0035
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 · uneditedSQL injection vulnerability in register.php for Phorum 3.4.5 and earlier allows remote attackers to execute arbitrary SQL commands via the hide_email parameter.
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 confidenceSQL injection vulnerability in Phorum 3.4.5 and earlier allows remote attackers to execute arbitrary SQL commands via the unhvalidated hide_email parameter in register.php. This is a classic SQL injection flaw where user-supplied input is directly incorporated into SQL queries without proper sanitization or parameterization.
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<= 3.4.5CVSS 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.
-
Identify Phorum versionLocate the Phorum installation directory and find the version file or check the version information in the admin control panel. Common locations include a version.php file or the main index file.Affected if The installed version is 3.4.5 or any earlier version (3.4.x where x is less than 5, or any 3.x release before 3.4.5)
-
Verify register.php existsCheck if register.php exists in the Phorum web directory. This file handles user registration and contains the vulnerable hide_email parameter.Affected if register.php is present and accessible via the web server
-
Confirm hide_email parameter handlingInspect the register.php file to confirm it processes a hide_email parameter that gets incorporated into SQL queries without proper sanitization or parameterized queries.Affected if The hide_email parameter from register.php is directly used in SQL queries without input validation or parameterized queries
-
Determine exposureCheck if the registration functionality is enabled and accessible to remote users. An unauthenticated remote attacker needs to access the registration page to exploit this vulnerability.Affected if The Phorum registration page is publicly accessible and the hide_email parameter can be supplied via HTTP POST or GET requests
A user is affected if running Phorum version 3.4.5 or earlier with the register.php file accessible and the hide_email parameter being directly used in SQL queries without sanitization.
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 Phorum or implement proper input validation and parameterized queries for the hide_email parameter in register.php.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-0035 — 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-0035 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