CVE-2017-6819: CSRF

Published Mar 12, 2017
·
Updated

In WordPress before 4.7.3, there is cross-site request forgery (CSRF) in Press This (wp-admin/includes/class-wp-press-this.php), leading to excessive use of server resources. The CSRF can trigger an outbound HTTP request for a large file that is then parsed by Press This.

Affected Software

1 affected component
WordPress<=4.7.2

Event History

Mar 12, 2017
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
Data Sourced
via NVD·01:59 AM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2017-6819?

CVE-2017-6819 is considered a medium severity vulnerability due to its potential to cause excessive resource usage on affected servers.

2

How do I fix CVE-2017-6819?

To fix CVE-2017-6819, it is recommended to update WordPress to version 4.7.3 or later.

3

What does CVE-2017-6819 affect?

CVE-2017-6819 affects WordPress versions prior to 4.7.3, specifically targeting the Press This feature.

4

What kind of attack does CVE-2017-6819 enable?

CVE-2017-6819 enables cross-site request forgery (CSRF) attacks that can trigger excessive HTTP requests.

5

Who is impacted by CVE-2017-6819?

Any user running WordPress version 4.7.2 or earlier is impacted by CVE-2017-6819.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203