CVE-2005-1096
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 main.asp for Ocean12 Membership Manager Pro 1.x allows remote attackers to execute arbitrary SQL commands via the UserID 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 Ocean12 Membership Manager Pro 1.x allows remote attackers to inject arbitrary SQL commands through the UserID parameter in main.asp. The application fails to properly sanitize user input before using it in database queries, enabling attackers to manipulate SQL statements.
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 dataall versionsCVSS 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 Ocean12 Membership Manager Pro is installedSearch the web server for files or directories containing 'ocean12' or 'membership' in the file path, or check the application's default installation directory for the presence of ASP files belonging to Ocean12 Membership Manager Pro.Affected if The software is identified as Ocean12 Technologies Membership Manager Pro version 1.x on the system.
-
Locate the vulnerable main.asp fileSearch for main.asp in the web root or application directories of the installed Ocean12 software.Affected if main.asp exists in the application directory and is accessible via the web server.
-
Verify the UserID parameter handlingExamine the source code of main.asp (or retrieve it via view-source) and search for database query code that uses the UserID request parameter without proper sanitization or parameterized queries.Affected if The code shows direct inclusion of Request.QueryString("UserID") or Request.Form("UserID") in SQL queries without using parameterized queries, prepared statements, or input validation functions.
-
Test for SQL injection vulnerabilitySend an HTTP request to main.asp with a malicious SQL payload in the UserID parameter, such as UserID=1' OR '1'='1, and observe if the application returns database errors or unexpected data.Affected if The application returns SQL syntax errors, different content than expected, or allows authentication bypass based on the injected payload.
The system is affected if Ocean12 Membership Manager Pro 1.x is installed, main.asp is accessible, and the UserID parameter is used in SQL queries without parameterized statements or 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 dataImplement parameterized queries or prepared statements for all database queries using the UserID parameter, and add proper input validation to reject malicious SQL injection payloads.
- 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-1096 — 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-1096 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