CVE-2009-0402
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 client/new_account.php in Domain Technologie Control (DTC) before 0.29.16 allows remote attackers to execute arbitrary SQL commands via the (1) familyname, (2) christname, (3) company_name, (4) is_company, (5) email, (6) phone, (7) fax, (8) addr1, (9) addr2, (10) addr3, (11) zipcode, (12) city, (13) state, (14) country, and (15) vat_num 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 vulnerability in Domain Technologie Control (DTC) client/new_account.php allows remote attackers to execute arbitrary SQL commands through 15 form parameters (familyname, christname, company_name, is_company, email, phone, fax, addr1, addr2, addr3, zipcode, city, state, country, vat_num) in versions before 0.29.16.
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<= 0.29.8= 0.26.7= 0.26.8= 0.26.9= 0.27.3= 0.28.2= 0.28.3= 0.28.10= 0.29.1CVSS 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.
-
Identify installed DTC versionCheck the DTC version installed on your system. This is typically visible in the software's admin panel, or via command line tools used during installation (e.g., dpkg -l dtc, rpm -qi dtc, or checking /usr/share/dtc/VERSION).Affected if The installed version matches any of these: <= 0.29.8, = 0.26.7, = 0.26.8, = 0.26.9, = 0.27.3, = 0.28.2, = 0.28.3, = 0.28.10, = 0.29.1
-
Verify client/new_account.php existsLocate the file client/new_account.php in your DTC web root directory. Common paths include /var/www/html/dtc/client/new_account.php or within the DTC installation directory under htdocs/client/.Affected if The file client/new_account.php exists on the server in the web-accessible directory.
-
Confirm web interface accessibilityTest if the DTC client interface is accessible over the network by navigating to your DTC server URL with the path /client/new_account.php or /dtc/client/new_account.php in a web browser.Affected if The web interface at client/new_account.php is accessible from the network (remote attackers need this access to exploit the SQL injection).
-
Inspect vulnerable parameter usage in source codeExamine the source code of client/new_account.php and look for SQL query construction that uses the parameters: familyname, christname, company_name, is_company, email, phone, fax, addr1, addr2, addr3, zipcode, city, state, country, vat_num without parameterized queries or proper escaping.Affected if The code uses these form parameters directly in SQL queries without parameterized statements or input sanitization functions.
You are affected if your DTC version is one of the listed affected versions AND client/new_account.php is accessible over the web AND the source code uses the vulnerable parameters in unparameterized SQL queries.
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 dataUpgrade to DTC version 0.29.16 or later to obtain the patched code, or implement parameterized queries and input validation/sanitization on all user-supplied parameters in client/new_account.php.
- 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-2009-0402 — 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-2009-0402 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