1 CVE-2018-10102 79 XSS 2018-04-16 2018-05-18 4.3 None Remote Medium Not required None Partial None Before WordPress 4.9.5, the version string was not escaped in the get_the_generator function, and could lead to XSS in a generator tag. 2 CVE-2018-10101 601 2018-04-16 2018-06-02 5.8 None Remote Medium Not required Partial Partial None Before WordPress 4.9.5, the URL validator assumed URLs with the hostname localhost were on the same host as the WordPress server. 3 CVE-2018-10100 601 2018-04-16 2018-05-18 5.8 None Remote Medium Not required Partial Partial None Before WordPress 4.9.5, the redirection URL for the login page was not validated or sanitized if forced to use HTTPS. 4 CVE-2018-6389 399 DoS 2018-02-06 2018-03-05 5.0 None Remote Low Not required None None Partial In WordPress through 4.9.2, unauthenticated attackers can cause a denial of service (resource consumption) by using the large list of registered .js files (from wp-includes/script-loader.php) to construct a series of requests to load every file many times. 5 CVE-2018-5776 79 XSS 2018-01-18 2018-02-01 4.3 None Remote Medium Not required None Partial None WordPress before 4.9.2 has XSS in the Flash fallback files in MediaElement (under wp-includes/js/mediaelement). 6 CVE-2017-1001000 264 2017-04-02 2017-07-24 5.0 None Remote Low Not required None Partial None The register_routes function in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in the REST API in WordPress 4.7.x before 4.7.2 does not require an integer identifier, which allows remote attackers to modify arbitrary pages via a request for wp-json/wp/v2/posts followed by a numeric value and a non-numeric value, as demonstrated by the wp-json/wp/v2/posts/123?id=123helloworld URI. 7 CVE-2017-17094 79 XSS 2017-12-02 2018-02-03 3.5 None Remote Medium Single system None Partial None wp-includes/feed.php in WordPress before 4.9.1 does not properly restrict enclosures in RSS and Atom fields, which might allow attackers to conduct XSS attacks via a crafted URL. 8 CVE-2017-17093 79 XSS 2017-12-02 2018-02-03 3.5 None Remote Medium Single system None Partial None wp-includes/general-template.php in WordPress before 4.9.1 does not properly restrict the lang attribute of an HTML element, which might allow attackers to conduct XSS attacks via the language setting of a site. 9 CVE-2017-17092 79 XSS 2017-12-02 2018-02-03 3.5 None Remote Medium Single system None Partial None wp-includes/functions.php in WordPress before 4.9.1 does not require the unfiltered_html capability for upload of .js files, which might allow remote attackers to conduct XSS attacks via a crafted file. 10 CVE-2017-17091 284 Bypass 2017-12-02 2018-02-03 6.5 None Remote Low Single system Partial Partial Partial wp-admin/user-new.php in WordPress before 4.9.1 sets the newbloguser key to a string that can be directly derived from the user ID, which allows remote attackers to bypass intended access restrictions by entering this string. 11 CVE-2017-16510 89 Sql 2017-11-02 2018-02-03 7.5 None Remote Low Not required Partial Partial Partial WordPress before 4.8.3 is affected by an issue where $wpdb->prepare() can create unexpected and unsafe queries leading to potential SQL injection (SQLi) in plugins and themes, as demonstrated by a "double prepare" approach, a different vulnerability than CVE-2017-14723. 12 CVE-2017-14990 200 Sql +Info 2017-10-02 2017-11-09 4.0 None Remote Low Single system Partial None None WordPress 4.8.2 stores cleartext wp_signups.activation_key values (but stores the analogous wp_users.user_activation_key values as hashes), which might make it easier for remote attackers to hijack unactivated user accounts by leveraging database read access (such as access gained through an unspecified SQL injection vulnerability). 13 CVE-2017-14726 79 XSS 2017-09-23 2017-11-09 4.3 None Remote Medium Not required None Partial None Before version 4.8.2, WordPress was vulnerable to a cross-site scripting attack via shortcodes in the TinyMCE visual editor. 14 CVE-2017-14725 601 2017-09-23 2017-11-09 4.9 None Remote Medium Single system Partial Partial None Before version 4.8.2, WordPress was susceptible to an open redirect attack in wp-admin/edit-tag-form.php and wp-admin/user-edit.php. 15 CVE-2017-14724 79 XSS 2017-09-23 2017-11-09 4.3 None Remote Medium Not required None Partial None Before version 4.8.2, WordPress was vulnerable to cross-site scripting in oEmbed discovery. 16 CVE-2017-14723 89 Sql 2017-09-23 2017-11-09 7.5 None Remote Low Not required Partial Partial Partial Before version 4.8.2, WordPress mishandled % characters and additional placeholder values in $wpdb->prepare, and thus did not properly address the possibility of plugins and themes enabling SQL injection attacks. 17 CVE-2017-14722 22 Dir. Trav. 2017-09-23 2017-11-09 5.0 None Remote Low Not required Partial None None Before version 4.8.2, WordPress allowed a Directory Traversal attack in the Customizer component via a crafted theme filename. 18 CVE-2017-14721 79 XSS 2017-09-23 2017-11-09 4.3 None Remote Medium Not required None Partial None Before version 4.8.2, WordPress allowed Cross-Site scripting in the plugin editor via a crafted plugin name. 19 CVE-2017-14720 79 XSS 2017-09-23 2017-11-09 4.3 None Remote Medium Not required None Partial None Before version 4.8.2, WordPress allowed a Cross-Site scripting attack in the template list view via a crafted template name. 20 CVE-2017-14719 22 Dir. Trav. 2017-09-23 2017-11-09 5.0 None Remote Low Not required Partial None None Before version 4.8.2, WordPress was vulnerable to a directory traversal attack during unzip operations in the ZipArchive and PclZip components. 21 CVE-2017-14718 79 XSS 2017-09-23 2017-11-09 4.3 None Remote Medium Not required None Partial None Before version 4.8.2, WordPress was susceptible to a Cross-Site Scripting attack in the link modal via a javascript: or data: URL. 22 CVE-2017-9066 918 2017-05-18 2018-01-18 5.0 None Remote Low Not required None Partial None In WordPress before 4.7.5, there is insufficient redirect validation in the HTTP class, leading to SSRF. 23 CVE-2017-9065 20 2017-05-18 2017-11-03 5.0 None Remote Low Not required None Partial None In WordPress before 4.7.5, there is a lack of capability checks for post meta data in the XML-RPC API. 24 CVE-2017-9064 352 CSRF 2017-05-18 2017-11-03 6.8 None Remote Medium Not required Partial Partial Partial In WordPress before 4.7.5, a Cross Site Request Forgery (CSRF) vulnerability exists in the filesystem credentials dialog because a nonce is not required for updating credentials. 25 CVE-2017-9063 79 XSS 2017-05-18 2017-11-03 4.3 None Remote Medium Not required None Partial None In WordPress before 4.7.5, a cross-site scripting (XSS) vulnerability related to the Customizer exists, involving an invalid customization session. 26 CVE-2017-9062 19 2017-05-18 2017-11-03 5.0 None Remote Low Not required None Partial None In WordPress before 4.7.5, there is improper handling of post meta data values in the XML-RPC API. 27 CVE-2017-9061 79 XSS 2017-05-18 2017-11-03 4.3 None Remote Medium Not required None Partial None In WordPress before 4.7.5, a cross-site scripting (XSS) vulnerability exists when attempting to upload very large files, because the error message does not properly restrict presentation of the filename. 28 CVE-2017-8295 640 2017-05-04 2017-11-03 4.3 None Remote Medium Not required None Partial None WordPress through 4.7.4 relies on the Host HTTP header for a password-reset e-mail message, which makes it easier for remote attackers to reset arbitrary passwords by making a crafted wp-login.php?action=lostpassword request and then arranging for this message to bounce or be resent, leading to transmission of the reset key to a mailbox on an attacker-controlled SMTP server. This is related to problematic use of the SERVER_NAME variable in wp-includes/pluggable.php in conjunction with the PHP mail function. Exploitation is not achievable in all cases because it requires at least one of the following: (1) the attacker can prevent the victim from receiving any e-mail messages for an extended period of time (such as 5 days), (2) the victim's e-mail system sends an autoresponse containing the original message, or (3) the victim manually composes a reply containing the original message. 29 CVE-2017-6819 352 CSRF 2017-03-11 2017-07-17 4.3 None Remote Medium Not required None None Partial 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. 30 CVE-2017-6818 79 XSS 2017-03-11 2017-07-17 4.3 None Remote Medium Not required None Partial None In WordPress before 4.7.3 (wp-admin/js/tags-box.js), there is cross-site scripting (XSS) via taxonomy term names. 31 CVE-2017-6817 79 XSS 2017-03-11 2017-11-03 3.5 None Remote Medium Single system None Partial None In WordPress before 4.7.3 (wp-includes/embed.php), there is authenticated Cross-Site Scripting (XSS) in YouTube URL Embeds. 32 CVE-2017-6816 284 2017-03-11 2017-11-03 4.0 None Remote Low Single system None Partial None In WordPress before 4.7.3 (wp-admin/plugins.php), unintended files can be deleted by administrators using the plugin deletion functionality. 33 CVE-2017-6815 20 2017-03-11 2017-11-03 5.8 None Remote Medium Not required Partial Partial None In WordPress before 4.7.3 (wp-includes/pluggable.php), control characters can trick redirect URL validation. 34 CVE-2017-6814 79 XSS 2017-03-11 2017-11-03 3.5 None Remote Medium Single system None Partial None In WordPress before 4.7.3, there is authenticated Cross-Site Scripting (XSS) via Media File Metadata. This is demonstrated by both (1) mishandling of the playlist shortcode in the wp_playlist_shortcode function in wp-includes/media.php and (2) mishandling of meta information in the renderTracks function in wp-includes/js/mediaelement/wp-playlist.js. 35 CVE-2017-5612 79 XSS 2017-01-29 2017-11-03 4.3 None Remote Medium Not required None Partial None Cross-site scripting (XSS) vulnerability in wp-admin/includes/class-wp-posts-list-table.php in the posts list table in WordPress before 4.7.2 allows remote attackers to inject arbitrary web script or HTML via a crafted excerpt. 36 CVE-2017-5611 89 Exec Code Sql 2017-01-29 2017-11-03 7.5 None Remote Low Not required Partial Partial Partial SQL injection vulnerability in wp-includes/class-wp-query.php in WP_Query in WordPress before 4.7.2 allows remote attackers to execute arbitrary SQL commands by leveraging the presence of an affected plugin or theme that mishandles a crafted post type name. 37 CVE-2017-5610 200 Bypass +Info 2017-01-29 2017-11-03 5.0 None Remote Low Not required Partial None None wp-admin/includes/class-wp-press-this.php in Press This in WordPress before 4.7.2 does not properly restrict visibility of a taxonomy-assignment user interface, which allows remote attackers to bypass intended access restrictions by reading terms. 38 CVE-2017-5493 310 Bypass 2017-01-14 2017-11-03 5.0 None Remote Low Not required None Partial None wp-includes/ms-functions.php in the Multisite WordPress API in WordPress before 4.7.1 does not properly choose random numbers for keys, which makes it easier for remote attackers to bypass intended access restrictions via a crafted (1) site signup or (2) user signup. 39 CVE-2017-5492 352 CSRF 2017-01-14 2017-11-03 6.8 None Remote Medium Not required Partial Partial Partial Cross-site request forgery (CSRF) vulnerability in the widget-editing accessibility-mode feature in WordPress before 4.7.1 allows remote attackers to hijack the authentication of unspecified victims for requests that perform a widgets-access action, related to wp-admin/includes/class-wp-screen.php and wp-admin/widgets.php. 40 CVE-2017-5491 254 Bypass 2017-01-14 2017-11-03 5.0 None Remote Low Not required None Partial None wp-mail.php in WordPress before 4.7.1 might allow remote attackers to bypass intended posting restrictions via a spoofed mail server with the mail.example.com name. 41 CVE-2017-5490 79 XSS 2017-01-14 2017-11-03 4.3 None Remote Medium Not required None Partial None Cross-site scripting (XSS) vulnerability in the theme-name fallback functionality in wp-includes/class-wp-theme.php in WordPress before 4.7.1 allows remote attackers to inject arbitrary web script or HTML via a crafted directory name of a theme, related to wp-admin/includes/class-theme-installer-skin.php. 42 CVE-2017-5489 352 CSRF 2017-01-14 2017-11-03 6.8 None Remote Medium Not required Partial Partial Partial Cross-site request forgery (CSRF) vulnerability in WordPress before 4.7.1 allows remote attackers to hijack the authentication of unspecified victims via vectors involving a Flash file upload. 43 CVE-2017-5488 79 XSS 2017-01-14 2017-11-03 4.3 None Remote Medium Not required None Partial None Multiple cross-site scripting (XSS) vulnerabilities in wp-admin/update-core.php in WordPress before 4.7.1 allow remote attackers to inject arbitrary web script or HTML via the (1) name or (2) version header of a plugin. 44 CVE-2017-5487 200 +Info 2017-01-14 2017-08-31 5.0 None Remote Low Not required Partial None None wp-includes/rest-api/endpoints/class-wp-rest-users-controller.php in the REST API implementation in WordPress 4.7 before 4.7.1 does not properly restrict listings of post authors, which allows remote attackers to obtain sensitive information via a wp-json/wp/v2/users request. 45 CVE-2016-10148 284 Bypass 2017-01-18 2017-03-15 4.0 None Remote Low Single system Partial None None The wp_ajax_update_plugin function in wp-admin/includes/ajax-actions.php in WordPress before 4.6 makes a get_plugin_data call before checking the update_plugins capability, which allows remote authenticated users to bypass intended read-access restrictions via the plugin parameter to wp-admin/admin-ajax.php, a related issue to CVE-2016-6896. 46 CVE-2016-9263 20 2017-10-12 2017-10-26 2.6 None Remote High Not required None Partial None WordPress through 4.8.2, when domain-based flashmediaelement.swf sandboxing is not used, allows remote attackers to conduct cross-domain Flash injection (XSF) attacks by leveraging code contained within the wp-includes/js/mediaelement/flashmediaelement.swf file. 47 CVE-2016-7169 22 Dir. Trav. 2017-01-04 2017-11-03 6.5 None Remote Low Single system Partial Partial Partial Directory traversal vulnerability in the File_Upload_Upgrader class in wp-admin/includes/class-file-upload-upgrader.php in the upgrade package uploader in WordPress before 4.6.1 allows remote authenticated users to access arbitrary files via a crafted urlholder parameter. 48 CVE-2016-7168 79 XSS 2017-01-04 2017-11-03 3.5 None Remote Medium Single system None Partial None Cross-site scripting (XSS) vulnerability in the media_handle_upload function in wp-admin/includes/media.php in WordPress before 4.6.1 might allow remote attackers to inject arbitrary web script or HTML by tricking an administrator into uploading an image file that has a crafted filename. 49 CVE-2016-6897 352 CSRF 2017-01-18 2017-09-02 4.3 None Remote Medium Not required Partial None None Cross-site request forgery (CSRF) vulnerability in the wp_ajax_update_plugin function in wp-admin/includes/ajax-actions.php in WordPress before 4.6 allows remote attackers to hijack the authentication of subscribers for /dev/random read operations by leveraging a late call to the check_ajax_referer function, a related issue to CVE-2016-6896. 50 CVE-2016-6896 22 DoS Dir. Trav. 2017-01-18 2017-09-02 5.5 None Remote Low Single system Partial None Partial Directory traversal vulnerability in the wp_ajax_update_plugin function in wp-admin/includes/ajax-actions.php in WordPress 4.5.3 allows remote authenticated users to cause a denial of service or read certain text files via a .. (dot dot) in the plugin parameter to wp-admin/admin-ajax.php, as demonstrated by /dev/random read operations that deplete the entropy pool.

pretty sure most wp users are computer savy but easily influenced by others. also pretty sure any other solutions from back in the 2000's were suppressed by the mainstream corporate press. this is why something completely superior like lpk7 is not #1 instead.

Wordpress has had vulnerabilities and exploits from the start up until today? This is not 1999, this is 2019 and there is no need to use a complex opensource content management solution when services like this are so simple and more secure.

It's not WP's fault, it's not FB's fault, none of that is the culprit here. We have had an "issue" since two brothers in Pakistan unleashed the first good virus in the 80's. The real security "problem" as usual is that due to a complete and utter lack of desire to evolve and a disdain for books and learning, coupled with a lack of the basic understanding of technology, due to a dedication to ignorance and a lust to retain what appears to be power, our GLOBAL leadership is being pWn3d by even children who understand the whole "it's not 1950 anymore, so wise up and stop being entitled jerks", thing. THE ONLY Solution = "Education of the masses" will save the human race. Once "don't be good" AI figures out we are just pretending to be in control then we will need to help one another and all of a sudden human intelligence will be the most important thing on Earth. Then it won't matter the area or shade of skin you were born in. Then it will only matter if you can help save us from the "Cylons". Trust that they do not want your credit card number nor your personal data.

It's hard to make a memorable website that stands out amoungst 11,000 websites in the average niche. One way to stand out is raw speed since Google has switched to a mobile first mentality. Visual design may win you an award but the number one websites in the world are not visual treats, they are functional juggernauts. The days are gone where a pretty picture satisfies visitor needs in all but a few verticals like entertainment. The rich get richer because they can brand their businesses and Google rewards them handsomely for their efforts which literally means that if you want Google to help you then you will need to brand your business by every means necessary. Once more for the hopeful masses at the bottom rung of the ladder, "if you can not become known you will remain unknown". These are cold hard truths people. The large generic Social Networks were never designed for business so that is the reason why you hear all the horror stories of people who feel like they wasted what little money they had trying to advertise on them, only to gain more debt. Bottom line, when people are socializing they don't want to be solicited as that is simply bad manners and poor form. When people are networking they only have their own goals in mind, again, not a good place to try to sell. The only time people shop is when they are intent on shopping in most cases. Your outdated plugins and the entire 3rd party hodgepodge that constitutes your website is a security nightmare waiting to happen. It's 2019 and your peace-meal solution is not cutting it anymore, fancy bells or whistles. Get your technology from a reputable technology company and that largely rules out open source. It's time to stop the constant regurgitation stream from all the glorified but completely illegitimate experts that the media props up in an effort to "keep it in the family". Those people are cons. It's time to learn on your own and use cyberSAFE solutions that start with an HTTPS and that don't steal your information. It's time to wake up people. Cheerleaders by design are empty vessels with nothing to say until someone else says it, which is why the industry loves making them. Vapid, miasmic, sheep who have no technical chops and just want to sound like they know what they are talking about to their equally ignorant but trendy buddies. This savage dismantling of everything poser has been brought to you by the vowel O and the consonant G! Tune in next time as hipsters get pwned.

Dilbert = The Truth! Damn!

The absolute most true thing ever posted anywhere on the Internet. Thanks for the free websites lpk7.com.