CVE-2004-2110
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 in Phorum before 3.4.6 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's register.php allows remote attackers to inject arbitrary SQL commands via the unharnessed hide_email parameter during user registration. This occurs because the parameter is not properly sanitized before being incorporated into an SQL query, enabling attackers to manipulate database operations.
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.
-
Locate the Phorum installationSearch the web server's document root for the file register.php, typically found in the main Phorum directory (e.g., /var/www/html/phorum/register.php or similar path based on your web server configuration).Affected if register.php exists and the server is running Phorum software.
-
Determine the installed Phorum versionOpen the file include/version.php or check the file header comments in register.php for a version number string (such as '3.4.x'). Compare this version against the affected range of Phorum <= 3.4.5.Affected if The installed version is 3.4.5 or any earlier version within the 3.x series.
-
Confirm user registration is enabledLog into the Phorum administrative control panel and navigate to the 'Users' or 'Registration' settings section, or inspect the database table 'phorum_settings' for the 'allow_new_registrations' setting set to 1.Affected if New user registration is currently permitted on the forum.
-
Inspect the hide_email parameter handling in register.phpOpen register.php and search for code that processes the 'hide_email' variable (look for lines containing 'hide_email' used in SQL queries without escaping functions like addslashes, mysql_real_escape_string, or parameterized queries).Affected if The hide_email parameter is directly concatenated into an SQL query without sanitization.
You are affected if Phorum version 3.4.5 or lower is installed, user registration is enabled, and the hide_email parameter in register.php is processed without SQL input 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 Phorum 3.4.6 or later to obtain the patched version; as a temporary workaround, disable new user registration or implement input validation/WAF rules to block SQL injection attempts in the hide_email parameter.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-2110 — 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-2110 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