CVEdetails.com the ultimate security vulnerability data source
(e.g.: CVE-2009-1234 or 2010-1234 or 20101234)
Log In   Register
  Take a third party risk management course for FREE
Vulnerability Feeds & WidgetsNew   www.itsecdb.com  

Wordpress » Wordpress : Security Vulnerabilities Published In 2019

CVSS Scores Greater Than: 0   1   2   3   4   5   6   7   8   9  
Press ESC to close
# CVE ID CWE ID # of Exploits Vulnerability Type(s) Publish Date Update Date Score Gained Access Level Access Complexity Authentication Conf. Integ. Avail.
1 CVE-2019-20043 269 Bypass 2019-12-27 2020-01-10
5.0
 None Remote Low Not required None Partial None
In in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in WordPress 3.7 to 5.3.0, authenticated users who do not have the rights to publish a post are able to mark posts as sticky or unsticky via the REST API. For example, the contributor role does not have such rights, but this allowed them to bypass that. This has been patched in WordPress 5.3.1, along with all the previous WordPress versions from 3.7 to 5.3 via a minor release.
2 CVE-2019-20042 79 XSS 2019-12-27 2020-01-10
4.3
 None Remote Medium Not required None Partial None
In wp-includes/formatting.php in WordPress 3.7 to 5.3.0, the function wp_targeted_link_rel() can be used in a particular way to result in a stored cross-site scripting (XSS) vulnerability. This has been patched in WordPress 5.3.1, along with all the previous WordPress versions from 3.7 to 5.3 via a minor release.
3 CVE-2019-20041 20 Bypass 2019-12-27 2020-01-08
7.5
 None Remote Low Not required Partial Partial Partial
wp_kses_bad_protocol in wp-includes/kses.php in WordPress before 5.3.1 mishandles the HTML5 colon named entity, allowing attackers to bypass input sanitization, as demonstrated by the javascript: substring.
4 CVE-2019-17675 352 CSRF 2019-10-17 2019-11-05
6.8
 None Remote Medium Not required Partial Partial Partial
WordPress before 5.2.4 does not properly consider type confusion during validation of the referer in the admin pages, possibly leading to CSRF.
5 CVE-2019-17674 79 XSS 2019-10-17 2020-01-08
3.5
 None Remote Medium ??? None Partial None
WordPress before 5.2.4 is vulnerable to stored XSS (cross-site scripting) via the Customizer.
6 CVE-2019-17673 2019-10-17 2022-03-31
5.0
 None Remote Low Not required None Partial None
WordPress before 5.2.4 is vulnerable to poisoning of the cache of JSON GET requests because certain requests lack a Vary: Origin header.
7 CVE-2019-17672 79 XSS 2019-10-17 2020-01-08
4.3
 None Remote Medium Not required None Partial None
WordPress before 5.2.4 is vulnerable to a stored XSS attack to inject JavaScript into STYLE elements.
8 CVE-2019-17671 200 +Info 2019-10-17 2019-11-05
5.0
 None Remote Low Not required Partial None None
In WordPress before 5.2.4, unauthenticated viewing of certain content is possible because the static query property is mishandled.
9 CVE-2019-17670 918 2019-10-17 2020-09-11
7.5
 None Remote Low Not required Partial Partial Partial
WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because Windows paths are mishandled during certain validation of relative URLs.
10 CVE-2019-17669 918 2019-10-17 2019-11-05
7.5
 None Remote Low Not required Partial Partial Partial
WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because URL validation does not consider the interpretation of a name as a series of hex characters.
11 CVE-2019-16781 79 Exec Code XSS 2019-12-26 2020-01-08
3.5
 None Remote Medium ??? None Partial None
In WordPress before 5.3.1, authenticated users with lower privileges (like contributors) can inject JavaScript code in the block editor, which is executed within the dashboard. It can lead to an admin opening the affected post in the editor leading to XSS.
12 CVE-2019-16780 79 Exec Code XSS 2019-12-26 2020-01-08
3.5
 None Remote Medium ??? None Partial None
WordPress users with lower privileges (like contributors) can inject JavaScript code in the block editor using a specific payload, which is executed within the dashboard. This can lead to XSS if an admin opens the post in the editor. Execution of this attack does require an authenticated user. This has been patched in WordPress 5.3.1, along with all the previous WordPress versions from 3.7 to 5.3 via a minor release. Automatic updates are enabled by default for minor releases and we strongly recommend that you keep them enabled.
13 CVE-2019-16223 79 XSS 2019-09-11 2021-01-04
3.5
 None Remote Medium ??? None Partial None
WordPress before 5.2.3 allows XSS in post previews by authenticated users.
14 CVE-2019-16222 79 XSS 2019-09-11 2019-09-12
4.3
 None Remote Medium Not required None Partial None
WordPress before 5.2.3 has an issue with URL sanitization in wp_kses_bad_protocol_once in wp-includes/kses.php that can lead to cross-site scripting (XSS) attacks.
15 CVE-2019-16221 79 XSS 2019-09-11 2019-09-12
4.3
 None Remote Medium Not required None Partial None
WordPress before 5.2.3 allows reflected XSS in the dashboard.
16 CVE-2019-16220 601 2019-09-11 2019-09-12
5.8
 None Remote Medium Not required Partial Partial None
In WordPress before 5.2.3, validation and sanitization of a URL in wp_validate_redirect in wp-includes/pluggable.php could lead to an open redirect.
17 CVE-2019-16219 79 XSS 2019-09-11 2019-09-12
4.3
 None Remote Medium Not required None Partial None
WordPress before 5.2.3 allows XSS in shortcode previews.
18 CVE-2019-16218 79 XSS 2019-09-11 2019-09-15
4.3
 None Remote Medium Not required None Partial None
WordPress before 5.2.3 allows XSS in stored comments.
19 CVE-2019-16217 79 XSS 2019-09-11 2019-10-17
4.3
 None Remote Medium Not required None Partial None
WordPress before 5.2.3 allows XSS in media uploads because wp_ajax_upload_attachment is mishandled.
20 CVE-2019-9787 352 Exec Code XSS CSRF 2019-03-14 2019-03-31
6.8
 None Remote Medium Not required Partial Partial Partial
WordPress before 5.1.1 does not properly filter comment content, leading to Remote Code Execution by unauthenticated users in a default configuration. This occurs because CSRF protection is mishandled, and because Search Engine Optimization of A elements is performed incorrectly, leading to XSS. The XSS results in administrative access, which allows arbitrary changes to .php files. This is related to wp-admin/includes/ajax-actions.php and wp-includes/comment.php.
21 CVE-2019-8943 22 Dir. Trav. 2019-02-20 2021-02-23
4.0
 None Remote Low ??? None Partial None
WordPress through 5.0.3 allows Path Traversal in wp_crop_image(). An attacker (who has privileges to crop an image) can write the output image to an arbitrary directory via a filename containing two image extensions and ../ sequences, such as a filename ending with the .jpg?/../../file.jpg substring.
22 CVE-2019-8942 94 Exec Code 2019-02-20 2021-07-21
6.5
 None Remote Low ??? Partial Partial Partial
WordPress before 4.9.9 and 5.x before 5.0.1 allows remote code execution because an _wp_attached_file Post Meta entry can be changed to an arbitrary string, such as one ending with a .jpg?file.php substring. An attacker with author privileges can execute arbitrary code by uploading a crafted image containing PHP code in the Exif metadata. Exploitation can leverage CVE-2019-8943.
23 CVE-2017-6514 200 +Info 2019-05-22 2019-05-27
5.0
 None Remote Low Not required Partial None None
WordPress 4.7.2 mishandles listings of post authors, which allows remote attackers to obtain sensitive information (Path Disclosure) via a /wp-json/oembed/1.0/embed?url= request, related to the "author_name":" substring.
Total number of vulnerabilities : 23   Page : 1 (This Page)
CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site. OVAL is a registered trademark of The MITRE Corporation and the authoritative source of OVAL content is MITRE's OVAL web site.
Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.