CVE-2019-16780
published 2019-12-26CVE-2019-16780: WordPress users with lower privileges (like contributors) can inject JavaScript code in the block editor using a specific payload, which is executed within the…
PriorityP430medium5.4CVSS 3.1
AVNACLPRLUIRSCCLILAN
EPSS
1.72%
74.9th percentile
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.
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | wordpress | < wordpress 5.3.2+dfsg1-1 (bookworm) | wordpress 5.3.2+dfsg1-1 (bookworm) |
| wordpress | wordpress | < 5.3.1 | 5.3.1 |
| wordpress | wordpress | — | — |
| wordpress | wordpress | >= 0 < 5.3.2+dfsg1-1 | 5.3.2+dfsg1-1 |
| wordpress | wordpress | >= 0 < 5.3.2+dfsg1-1 | 5.3.2+dfsg1-1 |
| wordpress | wordpress | >= 0 < 5.3.2+dfsg1-1 | 5.3.2+dfsg1-1 |
| wordpress | wordpress | >= 0 < 5.3.2+dfsg1-1 | 5.3.2+dfsg1-1 |
CVSS provenance
nvdv3.15.4MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
nvdv2.03.5LOWAV:N/AC:M/Au:S/C:N/I:P/A:N
osv5.4MEDIUM
vendor_debian5.8MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Debian
CVE-2019-16780: wordpress - WordPress users with lower privileges (like contributors) can inject JavaScript ...
vendor_debian·2019·CVSS 5.8
CVE-2019-16780 [MEDIUM] CVE-2019-16780: wordpress - WordPress users with lower privileges (like contributors) can inject JavaScript ...
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.
Scope: local
bookworm: resolved (fixed in 5.3.2+dfsg1-1)
bullseye: resolved (fixed in 5.3.2+dfsg1-1)
forky: resolved (fixed in 5.3.2+dfsg1-1)
sid: resolved (fixed in 5.3.2+dfsg1-1)
trixie: resolved (fixed in 5.3.2+dfsg1-1)
OSV
CVE-2019-16780: WordPress users with lower privileges (like contributors) can inject JavaScript code in the block editor using a specific payload, which is executed w
osv·2019-12-26·CVSS 5.4
CVE-2019-16780 [MEDIUM] CVE-2019-16780: WordPress users with lower privileges (like contributors) can inject JavaScript code in the block editor using a specific payload, which is executed w
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-16780 wordpress: XSS in WordPress block editor
bugzilla·2020-01-21·CVSS 5.8
CVE-2019-16780 [MEDIUM] CVE-2019-16780 wordpress: XSS in WordPress block editor
CVE-2019-16780 wordpress: XSS in WordPress block editor
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.
Reference:
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-x3wp-h3qx-9w94
Upstream commit:
https://github.com/WordPress/wordpress-develop/commit/505dd6a20b6fc3d06130018c1caeff764248c
Bugzilla
CVE-2019-16780 wordpress: XSS in WordPress block editor [epel-6]
bugzilla·2020-01-21·CVSS 5.8
CVE-2019-16780 [MEDIUM] CVE-2019-16780 wordpress: XSS in WordPress block editor [epel-6]
CVE-2019-16780 wordpress: XSS in WordPress block editor [epel-6]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-6.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to for the 'fedpkg update' re
Bugzilla
CVE-2019-16780 wordpress: XSS in WordPress block editor [epel-7]
bugzilla·2020-01-21·CVSS 5.8
CVE-2019-16780 [MEDIUM] CVE-2019-16780 wordpress: XSS in WordPress block editor [epel-7]
CVE-2019-16780 wordpress: XSS in WordPress block editor [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to for the 'fedpkg update' re
https://github.com/WordPress/wordpress-develop/commit/505dd6a20b6fc3d06130018c1caeff764248c29ehttps://github.com/WordPress/wordpress-develop/security/advisories/GHSA-x3wp-h3qx-9w94https://hackerone.com/reports/738644https://seclists.org/bugtraq/2020/Jan/8https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/https://wpvulndb.com/vulnerabilities/9976https://www.debian.org/security/2020/dsa-4599https://www.debian.org/security/2020/dsa-4677https://github.com/WordPress/wordpress-develop/commit/505dd6a20b6fc3d06130018c1caeff764248c29ehttps://github.com/WordPress/wordpress-develop/security/advisories/GHSA-x3wp-h3qx-9w94https://hackerone.com/reports/738644https://seclists.org/bugtraq/2020/Jan/8https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/https://wpvulndb.com/vulnerabilities/9976https://www.debian.org/security/2020/dsa-4599https://www.debian.org/security/2020/dsa-4677
2019-12-26
Published