CVE-2010-1994
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 index.php in TomatoCMS before 2.0.5 allows remote attackers to execute arbitrary SQL commands via the q parameter in conjunction with a /news/search PATH_INFO.
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 TomatoCMS index.php allows remote attackers to inject arbitrary SQL commands via the q parameter in the /news/search URL path. The application fails to properly sanitize user input before using it in SQL 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<= 2.0.4= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.3.1430= 2.0.3.1622CVSS 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 TomatoCMS installation and versionCheck the web root for TomatoCMS files. Look for a version identifier in files such as includes/config.php, VERSION.txt, or the admin dashboard footer which typically displays the version number.Affected if The installed version is 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.3.1430, 2.0.3.1622, or any version <= 2.0.4.
-
Confirm the news/search module existsVerify that the TomatoCMS installation includes the news module by checking for the presence of the /news/search URL path in the application's routing configuration or by attempting to access the search page.Affected if The news/search functionality is present and accessible on the system.
-
Inspect input sanitization for the q parameterExamine the PHP source code handling the /news/search route, specifically the index.php file or associated controller that processes the q parameter. Look for whether the parameter is used directly in SQL queries without proper escaping or prepared statements.Affected if The q parameter from the search URL is passed into SQL queries without sanitization, prepared statements, or parameterized binding.
-
Verify the vulnerability is presentReview the application code around line handling the search query in index.php or the news module. Confirm that user-supplied input from the q parameter is concatenated directly into SQL statements rather than being passed as a bound parameter.Affected if The code shows direct SQL query construction using the q parameter without sanitization functions such as mysql_real_escape_string, PDO prepared statements, or other input validation.
You are affected if TomatoCMS version 2.0.4 or lower is installed and the news search functionality uses the q parameter without sanitizing user input before executing 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 TomatoCMS 2.0.5 or later, or implement prepared statements/parameterized queries for the q parameter in the news search functionality. Input validation and escaping should also be applied as defense-in-depth.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1994 — 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-1994 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