CVE-2017-1000004
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 · uneditedATutor version 2.2.1 and earlier are vulnerable to a SQL injection in the Assignment Dropbox, BasicLTI, Blog Post, Blog, Group Course Email, Course Alumni, Course Enrolment, Group Membership, Course unenrolment, Course Enrolment List Search, Glossary, Social Group Member Search, Social Friend Search, Social Group Search, File Comment, Gradebook Test Title, User Group Membership, Inbox/Sent Items, Sent Messages, Links, Photo Album, Poll, Social Application, Social Profile, Test, Content Menu, Auto-Login, and Gradebook components resulting in information disclosure, database modification, or potential code execution.
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 ATutor LMS version 2.2.1 and earlier allows attackers to inject malicious SQL queries through unsanitized input in over 20 components (Assignment Dropbox, BasicLTI, Blog, Gradebook, User management, Inbox, and more). Successful exploitation enables information disclosure, database modification, or potentially remote code execution via database-level capabilities.
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.2.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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 the installed ATutor versionAccess the ATutor administration panel or check the version information file typically located in the installation directory. You can also check the login page footer or admin dashboard for version display.Affected if The installed version is 2.2.1 or any version prior to 2.2.2 (e.g., 2.2.0, 2.2, 2.1.x, 2.0.x, etc.)
-
Determine if vulnerable components are accessibleVerify which of the following components are enabled and accessible in your installation: Assignment Dropbox, BasicLTI integration, Blog, Gradebook, User management module, Inbox/messaging system, or any of the other 20+ affected components.Affected if Any of the known vulnerable components (Assignment Dropbox, BasicLTI, Blog, Gradebook, User management, Inbox, etc.) are enabled and accessible to users or attackers.
-
Check for unsanitized user input in vulnerable modulesInspect HTTP requests and responses when interacting with the affected components. Look for parameters that accept user input (such as search fields, form submissions, ID parameters, or filter options) and verify whether the application properly sanitizes special characters before using them in database queries.Affected if User-supplied input in any of the vulnerable components is directly incorporated into SQL queries without proper escaping or use of prepared statements.
-
Verify database error visibilityTest the affected components by submitting unexpected input (such as single quotes, UNION SELECT, or boolean-based payloads) and observe whether detailed database error messages are returned in the response.Affected if Database errors or SQL syntax error messages are displayed to users, indicating potential SQL injection points.
Your environment is affected if the installed ATutor version is 2.2.1 or earlier AND any of the vulnerable components (Assignment Dropbox, BasicLTI, Blog, Gradebook, User management, Inbox, etc.) are enabled and accessible without proper 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.
dbcve · scopedUpgrade to ATutor version 2.2.2 or later. If upgrade is not immediately possible, implement parameterized queries/Prepared Statements across all affected components and apply web application firewall rules to detect and block SQL injection attempts.
ATutor 2.2.2 or later
- 1. Backup your current ATutor database and files before making any changes
- 2. Download ATutor version 2.2.2 or later from the official ATutor website (www.atutor.ca)
- 3. Extract the new version files
- 4. Replace the existing ATutor installation files with the new version
- 5. Run any available database upgrade scripts included with the new version
- 6. Verify the installation by logging in and testing the affected components (Assignment Dropbox, Blog, Course Enrolment, Gradebook, etc.)
- 7. Check that the application is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000004 — 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-2017-1000004 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