CVE search
Every published CVE plus open-source advisories (NVD, OSV, GitHub), with CVSS, EPSS and whether it is being exploited in the wild (CISA KEV). Updated every few hours. Our scans match these against the technologies they detect.
Every published CVE plus open-source advisories (NVD, OSV, GitHub), with CVSS, EPSS and whether it is being exploited in the wild (CISA KEV). Updated every few hours. Our scans match these against the technologies they detect.
WordPress before 5.2.4 is vulnerable to poisoning of the cache of JSON GET requests because certain requests lack a Vary: Origin header. |
| 17/10/2019 |
| CVE-2019-17672 | 보통6.1 | WordPress before 5.2.4 is vulnerable to a stored XSS attack to inject JavaScript into STYLE elements. | 17/10/2019 |
| CVE-2019-17671 | 보통5.3 | In WordPress before 5.2.4, unauthenticated viewing of certain content is possible because the static query property is mishandled. | 17/10/2019 |
| CVE-2019-17670 | 심각9.8 | WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because Windows paths are mishandled during certain validation of relative URLs. | 17/10/2019 |
| CVE-2019-17669 | 심각9.8 | 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. | 17/10/2019 |
| CVE-2019-16223 | 보통5.4 | WordPress before 5.2.3 allows XSS in post previews by authenticated users. | 11/09/2019 |
| CVE-2019-16222 | 보통6.1 | 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. | 11/09/2019 |
| CVE-2019-16221 | 보통6.1 | WordPress before 5.2.3 allows reflected XSS in the dashboard. | 11/09/2019 |
| CVE-2019-16220 | 보통6.1 | 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 if a provided URL path does not start with a forward slash. | 11/09/2019 |
| CVE-2019-16219 | 보통6.1 | WordPress before 5.2.3 allows XSS in shortcode previews. | 11/09/2019 |
| CVE-2019-16218 | 보통6.1 | WordPress before 5.2.3 allows XSS in stored comments. | 11/09/2019 |
| CVE-2019-16217 | 보통6.1 | WordPress before 5.2.3 allows XSS in media uploads because wp_ajax_upload_attachment is mishandled. | 11/09/2019 |
| CVE-2017-6514 | 보통5.3 | 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. | 22/05/2019 |
| CVE-2019-9787 | 높음8.8 | 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 admi | 14/03/2019 |
| CVE-2019-8943 | 보통6.5 | 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. | 20/02/2019 |
| CVE-2019-8942 | 높음8.8 | 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 i | 20/02/2019 |
| CVE-2018-20153 | 보통5.4 | In WordPress before 4.9.9 and 5.x before 5.0.1, contributors could modify new comments made by users with greater privileges, possibly causing XSS. | 14/12/2018 |