CVE-2011-5071
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 Support Incident Tracker (aka SiT!) before 3.64 allow remote attackers to execute arbitrary SQL commands via the (1) exc[] parameter to report_marketing.php, (2) selected[] parameter to tasks.php, (3) sites[] parameter to billable_incidents.php, or (4) search_string parameter to search.php. NOTE: some of these details are obtained 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 confidenceMultiple SQL injection vulnerabilities exist in SiT! (Support Incident Tracker) versions prior to 3.64. The vulnerabilities allow remote attackers to inject arbitrary SQL commands through four parameters: exc[] in report_marketing.php, selected[] in tasks.php, sites[] in billable_incidents.php, and search_string in search.php. These appear to be classic SQL injection flaws where user-supplied input is not properly sanitized before being used in database 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<= 3.63= 3.6= 3.21= 3.22= 3.22pl1= 3.23= 3.24= 3.30= 3.31= 3.32= 3.33= 3.35CVSS 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 SiT! versionLocate the version file or check the application header/about page for the exact version number. Common locations include a version.php file or the main application dashboard.Affected if The installed version is 3.63 or lower, or matches any of these: 3.6, 3.21, 3.22, 3.22pl1, 3.23, 3.24, 3.30, 3.31, 3.32, 3.33, 3.35
-
Verify vulnerable PHP files existCheck for the presence of these files in the web root: report_marketing.php, tasks.php, billable_incidents.php, and search.php.Affected if Any of these four files exist in the application directory
-
Confirm PHP is processing these parametersReview the PHP source code of each affected file (report_marketing.php, tasks.php, billable_incidents.php, search.php) and search for direct use of the parameters exc[], selected[], sites[], and search_string in SQL queries without proper sanitization or prepared statements.Affected if The code shows these parameters being directly interpolated into SQL queries without escaping or parameterized queries
-
Check if application handles user inputVerify that the application accepts these parameters via GET or POST requests. Test by attempting to submit these parameters with test values to the affected pages.Affected if The application accepts and processes these parameters without rejecting potentially malicious SQL syntax
You are affected if you are running any SiT! version 3.63 or lower and the application exposes any of the four vulnerable parameters (exc[], selected[], sites[], search_string) through the corresponding PHP files without input sanitization.
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 SiT! version 3.64 or later. As an interim measure, implement input validation and use parameterized queries (prepared statements) for all database interactions involving user input in the affected files.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-5071 — 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-2011-5071 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