CVE-2005-1951
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 HTTP Response Splitting vulnerabilities in osCommerce 2.2 Milestone 2 and earlier allow remote attackers to spoof web content and poison web caches via hex-encoded CRLF ("%0d%0a") sequences in the (1) products_id or (2) pid parameter to index.php or (3) goto parameter to banner.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 confidenceHTTP Response Splitting vulnerability in osCommerce 2.2 and earlier allows remote attackers to inject malicious headers via hex-encoded CRLF sequences (%0d%0a) in the products_id, pid (index.php), or goto (banner.php) parameters. This enables web cache poisoning and content spoofing attacks.
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= 2.1= 2.2_cvs= 2.2_ms1= 2.2_ms2CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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 osCommerce installationLocate the osCommerce installation directory. Look for the main 'catalog' folder or check for the presence of 'install' and 'admin' directories with osCommerce-specific PHP files.Affected if osCommerce is installed on the server.
-
Identify osCommerce versionCheck the version.php file in the osCommerce directory, typically found at catalog/includes/application_top.php or catalog/admin/includes/application_top.php. Look for version constants like 'VERSION' or check the release notes file.Affected if The installed version is osCommerce 2.1, 2.2_cvs, 2.2_ms1, or 2.2_ms2.
-
Inspect index.php for vulnerable parametersOpen catalog/index.php and search for references to 'products_id' and 'pid' parameters in the code. Verify whether these parameters are used in HTTP header generation or redirect functions without sanitization.Affected if index.php processes products_id or pid parameters and includes them in HTTP headers without filtering %0d%0a sequences.
-
Inspect banner.php for vulnerable parametersOpen catalog/banner.php (or the equivalent banner handler file) and search for the 'goto' parameter. Check whether it is used in header() or setcookie() functions without validating for CRLF sequences.Affected if banner.php processes the goto parameter and includes it in HTTP headers without filtering %0d%0a sequences.
-
Test for input validationSearch the codebase for input filtering routines that handle the affected parameters. Look for code that explicitly removes, encodes, or blocks %0d%0a, \r\n, or chr(13).chr(10) before header generation.Affected if No input validation exists for the products_id, pid, or goto parameters, or validation is missing the hex-encoded form (%0d%0a).
The environment is affected if osCommerce 2.1 through 2.2_ms2 is installed and the index.php or banner.php scripts use the vulnerable parameters without filtering CRLF sequences from user input before including them in HTTP response headers.
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 dataSanitize user input by filtering or encoding CRLF characters (%0d%0a) before including in HTTP response headers. For legacy osCommerce 2.2 systems, consider upgrading to a supported version as no official patches are available for this end-of-life product.
- 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-1951 — 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-1951 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