CVE-2007-3575
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 includes/functions in FreeDomain.co.nr Clone allows remote attackers to execute arbitrary SQL commands via the logindomain parameter to members.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 confidenceSQL injection vulnerability in the logindomain parameter of members.php in FreeDomain.co.nr Clone allows remote attackers to execute arbitrary SQL commands via unsanitized user input passed to includes/functions.
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.0CVSS 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 the FreeDomain.co.nr Clone installationSearch for the file members.php in your web root directory. Also look for includes/functions.php in the same directory structure.Affected if The files members.php and includes/functions.php exist and belong to FreeDomain.co.nr Clone version 1.0
-
Verify the software versionCheck any version information in the source code comments, README files, or meta tags within members.php.Affected if The installed version is FreeDomain.co.nr Clone = 1.0
-
Inspect members.php for logindomain parameter handlingOpen members.php and search for references to 'logindomain' parameter in POST or GET requests. Verify whether this parameter is passed to includes/functions without sanitization.Affected if The logindomain parameter is received and forwarded to database operations without input validation or escaping
-
Examine includes/functions for SQL injection vulnerabilityOpen includes/functions.php and locate the SQL query that uses the logindomain parameter. Check if the parameter is directly concatenated into the SQL statement rather than using parameterized queries or escaping functions.Affected if The SQL query in includes/functions.php directly incorporates the logindomain value into the query string without prepared statements, parameter binding, or escaping functions such as mysql_real_escape_string
Your environment is affected if you are running FreeDomain.co.nr Clone version 1.0 and the logindomain parameter from members.php is being used in unsanitized SQL queries within includes/functions.php.
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 database operations, and add input validation/sanitization on all user-supplied parameters including logindomain.
- 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-2007-3575 — 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-2007-3575 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