CVE-2017-6066
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 has CSRF in admin/languages/edit/1/. The attacker can perform any Edit Language action, and can optionally insert XSS via the title 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in Subrion CMS 4.0.5's language editing functionality at admin/languages/edit/1/. An attacker can trick authenticated administrators into performing unintended Edit Language actions, and can also inject arbitrary JavaScript via the title parameter (XSS).
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.5CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Verify Subrion CMS versionCheck the installed Subrion CMS version by examining the version file (typically includes/version.php or similar), or look for version information in the admin dashboard under System Information or About section.Affected if The installed version is exactly 4.0.5 (no patches applied)
-
Confirm admin access to language editorNavigate to the language editing interface at admin/languages/edit/1/ while logged in as an administrator. Verify the page loads and allows language parameter editing.Affected if The language editing page at admin/languages/edit/1/ is accessible and functional with admin privileges
-
Inspect language edit form for CSRF protectionView the HTML source of the language edit form at admin/languages/edit/1/. Look for a hidden input field containing a CSRF token (commonly named 'token', 'csrf_token', or 'form_token') and verify the form submission includes this token.Affected if The form lacks a CSRF token field or the token is not validated server-side (absence of token field in HTML indicates vulnerability)
-
Test title parameter for XSS vulnerabilitySubmit a language edit request with a JavaScript payload in the title parameter (e.g., <script>alert(1)</script>). Then view the saved language entry or any admin page displaying this title to see if the script executes.Affected if The title parameter is not properly sanitized or encoded, allowing stored JavaScript to execute when the page is rendered
A system is affected if running Subrion CMS 4.0.5 with the language editing module accessible to administrators, and the edit form lacks CSRF token protection or the title parameter allows script 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 dataImplement anti-CSRF tokens in the language edit form and server-side validation, along with proper output encoding/sanitization for the title parameter to prevent XSS.
- 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-6066 — 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-6066 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