CVE-2010-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 · uneditedMultiple SQL injection vulnerabilities in searchmatch.php in ScriptsFeed Dating Software allow remote attackers to execute arbitrary SQL commands via the (1) txtgender and (2) txtlookgender parameters. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
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 exist in the searchmatch.php file of ScriptsFeed Dating Software. The txtgender and txtlookgender parameters are not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands. This is a classic SQL injection flaw where user-supplied input is directly concatenated into 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.
-
Locate ScriptsFeed Dating Software installationSearch your web server file system for directories or files containing 'scriptsfeed' or 'dating' in the path, or look for searchmatch.php in web-accessible directories.Affected if The software is found installed on the server.
-
Identify searchmatch.php fileFind the file named searchmatch.php within the ScriptsFeed installation directory. Common paths may include /searchmatch.php or within a /dating/ subdirectory.Affected if The searchmatch.php file exists in the web application.
-
Check txtgender parameter handlingOpen searchmatch.php and locate the code handling the 'txtgender' parameter. Look for SQL query construction - check if the parameter value is directly concatenated into the query string without using parameterized queries, prepared statements, or input sanitization functions.Affected if The txtgender parameter is used in SQL queries via direct string concatenation without escaping or parameterization.
-
Check txtlookgender parameter handlingIn the same searchmatch.php file, locate code handling the 'txtlookgender' parameter. Examine how it is incorporated into SQL statements - verify whether it is passed as a bound parameter or concatenated directly.Affected if The txtlookgender parameter is used in SQL queries via direct string concatenation without escaping or parameterization.
-
Verify SQL query construction methodSearch the file for SQL keywords (SELECT, INSERT, UPDATE, DELETE) near the parameter names. Look for patterns like $sql = "SELECT ... " . $_POST['txtgender'] or similar direct concatenation, versus using mysqli_prepare, PDO prepare, or binding functions.Affected if SQL queries concatenate user input from txtgender or txtlookgender without using prepared statements or proper escaping functions.
If ScriptsFeed Dating Software with searchmatch.php is present and the txtgender or txtlookgender parameters are used in SQL queries through direct concatenation rather than prepared statements, the environment is vulnerable to CVE-2010-1096.
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 (prepared statements) or proper input validation/sanitization for the txtgender and txtlookgender parameters in searchmatch.php to prevent SQL injection. Consider upgrading to a patched version of the software if available.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-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-2010-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