CVE-2017-6013
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 · uneditedSubrion CMS 4.0.5.10 has SQL injection in admin/database/ via the query 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 · high confidenceSQL injection vulnerability in Subrion CMS 4.0.5.10 in the admin panel's database module, specifically via the query parameter at admin/database/. Attackers can inject malicious SQL queries to exfiltrate, modify, or delete database contents.
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= 4.0.5.10CVSS 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.
-
Confirm Subrion CMS installationLook for Subrion CMS files in the web root directory. Check for known Subrion files like index.php, includes/loader.php, or admin/index.php. Identify the installation path.Affected if Subrion CMS is installed on the server
-
Identify Subrion CMS versionLocate the version file or configuration. Check files like includes/version.php, or similar version-related files in the Subrion installation directory. Compare the installed version to the affected version 4.0.5.10.Affected if The installed version is exactly 4.0.5.10
-
Check admin panel accessibilityAttempt to access the admin login page at /admin/ or /subrion/admin/ relative to the web root. Verify if the admin panel is reachable over the network.Affected if The admin panel is accessible without additional authentication barriers beyond login
-
Verify database module existsCheck if the database module file exists at the path corresponding to admin/database/ within the admin panel structure. Look for database-related admin files.Affected if The database module is present and accessible in the admin panel
-
Confirm query parameter handlingIf direct testing is authorized, send a benign SQL injection test payload to the admin/database/ endpoint via the query parameter. Monitor for SQL error responses or unexpected behavior.Affected if The endpoint processes SQL through the query parameter without sanitization
You are affected if Subrion CMS version 4.0.5.10 is installed and the admin panel with the database module is accessible on the network.
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 dataUpdate Subrion CMS to the latest patched version; until patched, restrict access to the admin panel to trusted IPs only and deploy WAF rules to block SQL injection patterns in query parameters.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6013 — 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-6013 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