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.
| Max Base Score | 6.1 |
| Published | 2019-12-27 |
| Updated | 2023-01-19 |
| EPSS | 0.28% |
WordPress before 5.2.4 is vulnerable to stored XSS (cross-site scripting) via the Customizer.
| Max Base Score | 5.4 |
| Published | 2019-10-17 |
| Updated | 2023-02-03 |
| EPSS | 0.22% |
WordPress before 5.2.4 is vulnerable to a stored XSS attack to inject JavaScript into STYLE elements.
| Max Base Score | 6.1 |
| Published | 2019-10-17 |
| Updated | 2023-02-03 |
| EPSS | 2.41% |
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.
| Max Base Score | 5.8 |
| Published | 2019-12-26 |
| Updated | 2023-01-19 |
| EPSS | 0.18% |
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.
| Max Base Score | 5.8 |
| Published | 2019-12-26 |
| Updated | 2022-11-23 |
| EPSS | 0.16% |
WordPress before 5.2.3 allows XSS in post previews by authenticated users.
| Max Base Score | 5.4 |
| Published | 2019-09-11 |
| Updated | 2022-10-07 |
| EPSS | 0.62% |
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.
| Max Base Score | 6.1 |
| Published | 2019-09-11 |
| Updated | 2023-01-31 |
| EPSS | 0.86% |
WordPress before 5.2.3 allows reflected XSS in the dashboard.
| Max Base Score | 6.1 |
| Published | 2019-09-11 |
| Updated | 2023-01-31 |
| EPSS | 1.46% |
WordPress before 5.2.3 allows XSS in shortcode previews.
| Max Base Score | 6.1 |
| Published | 2019-09-11 |
| Updated | 2023-01-31 |
| EPSS | 8.30% |
WordPress before 5.2.3 allows XSS in stored comments.
| Max Base Score | 6.1 |
| Published | 2019-09-11 |
| Updated | 2023-01-31 |
| EPSS | 1.46% |
WordPress before 5.2.3 allows XSS in media uploads because wp_ajax_upload_attachment is mishandled.
| Max Base Score | 6.1 |
| Published | 2019-09-11 |
| Updated | 2023-01-31 |
| EPSS | 1.51% |
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.
| Max Base Score | 8.8 |
| Published | 2019-03-14 |
| Updated | 2019-03-31 |
| EPSS | 86.36% |
12 vulnerabilities found