What is the severity of CVE-2017-8101?

CVE-2017-8101 has been classified as a medium severity vulnerability due to its potential impact on users' installations.

How do I fix CVE-2017-8101?

To fix CVE-2017-8101, update Serendipity to the latest version that addresses the CSRF vulnerability.

What type of attack does CVE-2017-8101 enable?

CVE-2017-8101 allows attackers to perform Cross-Site Request Forgery (CSRF) attacks to install any theme on the affected Serendipity installation.

Which version of Serendipity is affected by CVE-2017-8101?

CVE-2017-8101 specifically affects Serendipity version 2.0.5.

Is CVE-2017-8101 publicly known?

Yes, CVE-2017-8101 has been publicly disclosed and is documented in various security resources.

Vulnerability/
CVE-2017-8101

high

8.8

CWE

352

24/4/2017

27/4/2017

CVE-2017-8101: CSRF

First published: Mon Apr 24 2017(Updated: )

There is CSRF in Serendipity 2.0.5, allowing attackers to install any themes via a GET request.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Serendipity (S9Y) Freetag Event	=2.0.5

Remedy

http://seclists.org/fulldisclosure/2017/Apr/52

Remedy

https://github.com/s9y/Serendipity/issues/452

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-8101?
CVE-2017-8101 has been classified as a medium severity vulnerability due to its potential impact on users' installations.
How do I fix CVE-2017-8101?
To fix CVE-2017-8101, update Serendipity to the latest version that addresses the CSRF vulnerability.
What type of attack does CVE-2017-8101 enable?
CVE-2017-8101 allows attackers to perform Cross-Site Request Forgery (CSRF) attacks to install any theme on the affected Serendipity installation.
Which version of Serendipity is affected by CVE-2017-8101?
CVE-2017-8101 specifically affects Serendipity version 2.0.5.
Is CVE-2017-8101 publicly known?
Yes, CVE-2017-8101 has been publicly disclosed and is documented in various security resources.

agent/weakness
agent/severity
agent/references
agent/author
agent/description
agent/event
agent/type
agent/remedy
agent/last-modified-date
agent/softwarecombine
agent/first-publish-date
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/s9y
canonical/serendipity (s9y) freetag event
version/serendipity (s9y) freetag event/2.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-8101?
CVE-2017-8101 has been classified as a medium severity vulnerability due to its potential impact on users' installations.
How do I fix CVE-2017-8101?
To fix CVE-2017-8101, update Serendipity to the latest version that addresses the CSRF vulnerability.
What type of attack does CVE-2017-8101 enable?
CVE-2017-8101 allows attackers to perform Cross-Site Request Forgery (CSRF) attacks to install any theme on the affected Serendipity installation.
Which version of Serendipity is affected by CVE-2017-8101?
CVE-2017-8101 specifically affects Serendipity version 2.0.5.
Is CVE-2017-8101 publicly known?
Yes, CVE-2017-8101 has been publicly disclosed and is documented in various security resources.