CVE-2006-3275
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 profile.php in YaBB SE 1.5.5 and earlier allows remote attackers to execute SQL commands via a double-encoded user parameter in a viewprofile action.
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 YaBB SE 1.5.5 and earlier in profile.php allows remote attackers to execute arbitrary SQL commands via a double-encoded user parameter in a viewprofile action. The vulnerability stems from insufficient input sanitization that fails to properly handle double-encoded characters, allowing SQL injection payloads to bypass existing filters.
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.5.5= 1.5.1= 1.5.2= 1.5.4CVSS 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 YaBB SE installationSearch the web root for YaBB SE files, typically in directories named 'yabbse', 'forum', or at the root level. Look for characteristic files like index.php, profile.php, or YaBB.pl.Affected if YaBB SE software is present on the server
-
Identify installed YaBB SE versionCheck version.php or similar version file in the YaBB SE installation directory for a $ver or $version variable. Alternatively, view the HTML source of the forum homepage for version comments.Affected if Version is 1.5.5, 1.5.4, 1.5.2, or 1.5.1 (any version <= 1.5.5)
-
Verify profile.php exists and is accessibleLocate profile.php in the YaBB SE installation path (commonly at /profile.php or /yabbse/profile.php). Confirm the file exists and is readable.Affected if profile.php exists in the YaBB SE installation
-
Check for viewprofile action handlingExamine profile.php source code for any code handling the 'viewprofile' action or user parameter. Look for $_GET['action'] or $_POST['action'] references.Affected if The code processes a viewprofile action with a user parameter without proper decoding sanitization
-
Inspect SQL query handling in profile.phpSearch profile.php for SQL queries that incorporate the user parameter directly, such as SELECT statements using $_REQUEST['user'] or similar without parameterized queries or proper escaping.Affected if SQL queries concatenate user input directly without prepared statements or proper input validation
If YaBB SE version 1.5.5 or earlier is installed and profile.php processes a viewprofile action with user input via direct string concatenation, the environment is affected by CVE-2006-3275.
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 YaBB SE or apply input validation fixes to properly handle encoded characters and use parameterized queries instead of string concatenation for SQL queries in profile.php.
- 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-2006-3275 — 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-2006-3275 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