CVE-2019-6713
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 · uneditedapp\admin\controller\RouteController.php in ThinkCMF 5.0.190111 allows remote attackers to execute arbitrary PHP code by using vectors involving portal/List/index and list/:id to inject this code into data\conf\route.php, as demonstrated by a file_put_contents call.
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 confidenceThinkCMF 5.0.190111 contains a code injection vulnerability in app\admin\controller\RouteController.php. Attackers can inject arbitrary PHP code through portal/List/index and list/:id endpoints, which gets written to the data/conf/route.php configuration file. Once the malicious PHP code is written to this file, it can be executed, enabling full remote code execution on the server.
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= 5.0.190111CVSS 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 ThinkCMF installationLocate ThinkCMF by checking for characteristic directories such as app/admin/controller, public, data/conf, or the presence of index.php with ThinkCMF references.Affected if ThinkCMF framework is present in the environment.
-
Determine ThinkCMF versionCheck for a version file or configuration that displays the ThinkCMF version number. Typical locations include a version.php file, README, or the application bootstrap files.Affected if The installed version matches 5.0.190111 exactly.
-
Verify RouteController.php existsConfirm the file app/admin/controller/RouteController.php exists in the ThinkCMF installation directory.Affected if The vulnerable RouteController.php file is present.
-
Inspect route configuration fileExamine the contents of data/conf/route.php for any unexpected or obfuscated PHP code, particularly evaluate statements, system calls, or base64-decoded strings.Affected if The route.php file contains suspicious PHP code that was not intentionally added by administrators.
-
Check admin interface accessibilityDetermine if the /admin or /?s=admin endpoint is accessible from untrusted networks without authentication.Affected if The ThinkCMF admin panel is exposed to unauthenticated or untrusted network access.
A user is affected if ThinkCMF version 5.0.190111 is installed, the RouteController.php is present, and either the data/conf/route.php contains injected PHP code or the admin interface is accessible to untrusted users.
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 dataRestrict network access to the ThinkCMF admin interface to prevent unauthenticated access. If available, apply the vendor patch or upgrade to a patched ThinkCMF version.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6713 — 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-2019-6713 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