What is the severity of CVE-2017-6068?

The severity of CVE-2017-6068 is considered to be medium due to potential Cross-Site Request Forgery (CSRF) and Cross-Site Scripting (XSS) vulnerabilities.

How can I fix CVE-2017-6068?

To fix CVE-2017-6068, you should upgrade Subrion CMS to a version beyond 4.0.5 where this vulnerability has been addressed.

What systems are affected by CVE-2017-6068?

CVE-2017-6068 specifically affects Subrion CMS version 4.0.5.

Can CVE-2017-6068 lead to unauthorized content creation?

Yes, CVE-2017-6068 allows an attacker to create arbitrary blocks, which can be exploited to insert malicious content.

Is user action required to exploit CVE-2017-6068?

Exploitation of CVE-2017-6068 does not require user interaction, making it a critical concern for administrators.

Vulnerability/
CVE-2017-6068

high

8.8

CWE

352 79

27/3/2017

14/5/2022

5/8/2024

CVE-2017-6068: CSRF

First published: Mon Mar 27 2017(Updated: )

Subrion CMS 4.0.5 has CSRF in `admin/blocks/add/`. The attacker can create any block, and can optionally insert XSS via the content parameter.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
composer/intelliants/subrion	<=4.0.5
Subrion CMS	=4.0.5

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-6068?
The severity of CVE-2017-6068 is considered to be medium due to potential Cross-Site Request Forgery (CSRF) and Cross-Site Scripting (XSS) vulnerabilities.
How can I fix CVE-2017-6068?
To fix CVE-2017-6068, you should upgrade Subrion CMS to a version beyond 4.0.5 where this vulnerability has been addressed.
What systems are affected by CVE-2017-6068?
CVE-2017-6068 specifically affects Subrion CMS version 4.0.5.
Can CVE-2017-6068 lead to unauthorized content creation?
Yes, CVE-2017-6068 allows an attacker to create arbitrary blocks, which can be exploited to insert malicious content.
Is user action required to exploit CVE-2017-6068?
Exploitation of CVE-2017-6068 does not require user interaction, making it a critical concern for administrators.

collector/github-advisory-latest
alias/GHSA-q4h5-g3w8-f9x7
alias/CVE-2017-6068
collector/github-advisory
agent/weakness
agent/type
collector/mitre-cve
source/MITRE
agent/references
agent/severity
agent/last-modified-date
agent/description
agent/first-publish-date
agent/event
agent/trending
agent/source
agent/author
agent/softwarecombine
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-cve
package-manager/composer
vendor/intelliants
canonical/subrion cms
version/subrion cms/4.0.5

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-6068?
The severity of CVE-2017-6068 is considered to be medium due to potential Cross-Site Request Forgery (CSRF) and Cross-Site Scripting (XSS) vulnerabilities.
How can I fix CVE-2017-6068?
To fix CVE-2017-6068, you should upgrade Subrion CMS to a version beyond 4.0.5 where this vulnerability has been addressed.
What systems are affected by CVE-2017-6068?
CVE-2017-6068 specifically affects Subrion CMS version 4.0.5.
Can CVE-2017-6068 lead to unauthorized content creation?
Yes, CVE-2017-6068 allows an attacker to create arbitrary blocks, which can be exploited to insert malicious content.
Is user action required to exploit CVE-2017-6068?
Exploitation of CVE-2017-6068 does not require user interaction, making it a critical concern for administrators.