CVE-2005-0537
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 page.php for iGeneric (iG) Shop 1.2 may allow remote attackers to execute arbitrary SQL statements via the (1) cats, (2) l_price, or (3) u_price parameters.
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 vulnerabilities in page.php allow remote attackers to inject arbitrary SQL commands via the cats, l_price, and u_price parameters in iG Shop 1.2. The lack of proper input sanitization or parameterized queries enables attackers to manipulate 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= 1.2CVSS 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 Igeneric Free Shopping Cart installationSearch the web root directory for files or directories containing 'ig_shop', 'igeneric', or 'shopping cart' references. Check for a version file, readme, or installer that indicates the software name and version.Affected if The software is Igeneric Free Shopping Cart version 1.2 exactly.
-
Locate page.php in the applicationFind the page.php file within the web application directory structure. This is the identified vulnerable script.Affected if page.php exists in the application path.
-
Inspect the cats parameter handlingOpen page.php and search for references to the 'cats' parameter. Examine how this parameter is used in SQL queries - look for direct concatenation of user input into SQL statements without escaping or parameterization.Affected if The code directly incorporates the 'cats' parameter value into SQL queries without sanitization or prepared statements.
-
Inspect the l_price and u_price parametersIn page.php, locate handling of 'l_price' and 'u_price' parameters. Examine whether these values are filtered, escaped, or bound as parameters before being included in database queries.Affected if These parameters are used in SQL queries without proper escaping, type casting, or parameterized query binding.
-
Verify input validation is absentReview the code around the affected parameters for any input validation functions, whitelist checks, or sanitization routines. Look for functions like mysql_real_escape_string, htmlspecialchars used in SQL context, or any filtering logic.Affected if No input validation or sanitization functions are applied to cats, l_price, or u_price before SQL execution.
If Igeneric Free Shopping Cart version 1.2 is installed with page.php containing the vulnerable parameters used directly in SQL queries without sanitization, the environment is affected.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements for the affected parameters, and implement strict input validation on all user-supplied values.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-0537 — 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-0537 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