CVE-2006-0673
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 cms/index.php in Magic Calendar Lite 1.02, with magic_quotes_gpc disabled, allow remote attackers to execute arbitrary SQL commands via the (1) $total_login and (2) $total_password 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 Magic Calendar Lite 1.02 allows remote attackers to execute arbitrary SQL commands via the $total_login and $total_password parameters in cms/index.php when magic_quotes_gpc is disabled. The login credentials are directly concatenated into SQL queries without proper sanitization or parameterized 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.02CVSS 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.
-
Verify Magic Calendar Lite installationLocate the Magic Calendar Lite application on your web server. Check for a directory containing 'calendar' or 'magic calendar' related files, particularly looking for cms/index.phpAffected if The application Magic Calendar Lite is present on the server
-
Confirm the installed versionCheck the application version by examining version files, readme.txt, or the main PHP files for a version identifier like '1.02' or by comparing file hashes if availableAffected if The installed version is Magic Calendar Lite version 1.02
-
Identify the vulnerable script locationLocate the file cms/index.php within the Magic Calendar Lite installation directoryAffected if The file cms/index.php exists in the application
-
Check PHP configuration for magic_quotes_gpcCreate a PHP script with 'phpinfo();' or check your php.ini file to determine the current setting of magic_quotes_gpcAffected if magic_quotes_gpc is disabled (set to Off) in the PHP configuration
-
Inspect the SQL query implementationExamine the code in cms/index.php and look for direct concatenation of $total_login and $total_password variables into SQL queries without using prepared statements or escaping functionsAffected if The code directly concatenates user input ($total_login, $total_password) into SQL queries without sanitization
A user is affected if Magic Calendar Lite version 1.02 is installed with cms/index.php present and magic_quotes_gpc is disabled, allowing SQL injection through the login parameters.
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 dataEnable magic_quotes_gpc as a temporary workaround (deprecated in PHP 5.4+), or preferably refactor the application to use parameterized queries/prepared statements for all SQL queries involving user input.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-0673 — 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-2006-0673 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