CVE-2018-10225
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 · uneditedthinkphp 3.1.3 has SQL Injection via the index.php s 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 · moderate confidenceThinkPHP 3.1.3 contains a SQL injection vulnerability in the index.php entry point via the 's' parameter. This parameter is likely used for routing or module/action dispatch, and insufficient input sanitization allows arbitrary SQL command injection. The CRITICAL CVSS score indicates this is exploitable remotely without authentication.
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.1.3CVSS 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 ThinkPHP versionLocate the ThinkPHP core files (typically in the root directory or a vendor folder) and check the version file or changelog. Common locations include VERSION, ThinkPHP.php, or the vendor directory's thinkphp folder.Affected if The installed version is exactly 3.1.3 (or any version below 3.1.4 within the 3.x branch if the same vulnerable code path exists).
-
Verify application uses 's' parameter routingInspect your application's routing configuration and examine HTTP requests to see if the 's' parameter is used. Check the application's index.php entry point and any route configuration files for usage of $_GET['s'] or similar parameter handling.Affected if The application uses the 's' parameter for module/action dispatch or routing (this is common in default ThinkPHP 3.x installations).
-
Check input sanitization on 's' parameterExamine the application's code that processes the 's' parameter. Look in the dispatcher or routing logic (commonly in Core/Dispatcher.php or similar) to see if the parameter is passed to database queries without sanitization.Affected if The 's' parameter value is used directly in database queries or passed to model/database functions without proper escaping, prepared statements, or input filtering.
You are affected if you are running ThinkPHP 3.1.3 and your application uses the 's' parameter for routing without sanitization, allowing unauthenticated remote SQL injection.
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 ThinkPHP to a patched version (3.1.4 or later, or the latest 5.x branch). If immediate patching is not possible, implement web application firewall rules to filter malicious 's' parameter input containing SQL injection patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10225 — 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-2018-10225 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