What is the severity of CVE-2017-14845?

CVE-2017-14845 is classified as a high severity vulnerability due to its potential for SQL Injection attacks.

How do I fix CVE-2017-14845?

To fix CVE-2017-14845, it is recommended to update the WPCHUR Church Management System plugin to the latest version that addresses the vulnerability.

What systems are affected by CVE-2017-14845?

CVE-2017-14845 affects the WPCHUR Church Management System plugin for WordPress, specifically versions before the patch.

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

CVE-2017-14845 enables SQL Injection attacks via unsanitized input in the 'id' parameter, allowing unauthorized access to the database.

What should I do if I am compromised by CVE-2017-14845?

If compromised by CVE-2017-14845, immediate steps should include removing the vulnerable plugin, securing your database, and assessing for any data breaches.

Vulnerability/
CVE-2017-14845

high

8.8

CWE

28/9/2017

5/10/2017

CVE-2017-14845: SQL Injection

First published: Thu Sep 28 2017(Updated: )

Mojoomla WPCHURCH Church Management System for WordPress allows SQL Injection via the id parameter.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Church Management System

Never miss a vulnerability like this again

Reference Links

https://www.exploit-db.com/exploits/42800/

Frequently Asked Questions

What is the severity of CVE-2017-14845?
CVE-2017-14845 is classified as a high severity vulnerability due to its potential for SQL Injection attacks.
How do I fix CVE-2017-14845?
To fix CVE-2017-14845, it is recommended to update the WPCHUR Church Management System plugin to the latest version that addresses the vulnerability.
What systems are affected by CVE-2017-14845?
CVE-2017-14845 affects the WPCHUR Church Management System plugin for WordPress, specifically versions before the patch.
What type of attack does CVE-2017-14845 enable?
CVE-2017-14845 enables SQL Injection attacks via unsanitized input in the 'id' parameter, allowing unauthorized access to the database.
What should I do if I am compromised by CVE-2017-14845?
If compromised by CVE-2017-14845, immediate steps should include removing the vulnerable plugin, securing your database, and assessing for any data breaches.

agent/weakness
agent/references
agent/type
agent/description
agent/tags
agent/softwarecombine
agent/last-modified-date
agent/first-publish-date
collector/nvd-index
agent/software-canonical-lookup-request
agent/severity
agent/author
agent/event
vendor/dasinfomedia
canonical/church management system

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-14845?
CVE-2017-14845 is classified as a high severity vulnerability due to its potential for SQL Injection attacks.
How do I fix CVE-2017-14845?
To fix CVE-2017-14845, it is recommended to update the WPCHUR Church Management System plugin to the latest version that addresses the vulnerability.
What systems are affected by CVE-2017-14845?
CVE-2017-14845 affects the WPCHUR Church Management System plugin for WordPress, specifically versions before the patch.
What type of attack does CVE-2017-14845 enable?
CVE-2017-14845 enables SQL Injection attacks via unsanitized input in the 'id' parameter, allowing unauthorized access to the database.
What should I do if I am compromised by CVE-2017-14845?
If compromised by CVE-2017-14845, immediate steps should include removing the vulnerable plugin, securing your database, and assessing for any data breaches.