CVE-2019-16780 [Medium] | XSS in Wordpress

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-03-04	5.89%	3.61%	-2.28%
2	2026-03-01	3.61%	5.89%	+2.28%
3	2026-02-04	—	3.61%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-03-04

5.89%

3.61%

-2.28%

2026-03-01

3.61%

5.89%

+2.28%

2026-02-04

—

3.61%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.8	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	1.3	4.0	[email protected]
5.4	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.3	2.7	[email protected]
3.5	2.0	LOW	`AV:N/AC:M/Au:S/C:N/I:P/A:N` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:M) Exploitation needs some favorable conditions, but not exceptional ones. Authentication (AU:S) A single authentication is required. Confidentiality impact (C:N) No confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:N) No availability impact.	6.8	2.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.8

3.1

MEDIUM

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

1.3

4.0

[email protected]

5.4

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.3

2.7

[email protected]

3.5

2.0

LOW

AV:N/AC:M/Au:S/C:N/I:P/A:N Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:M): Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:S): A single authentication is required.
Confidentiality impact (C:N): No confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:N): No availability impact.

6.8

2.9

[email protected]

OS Trackers for CVE-2019-16780

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2019-16780 not yet assigned priority: Debian including 1 source packages (wordpress), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2019-16780
`ubuntu`	medium	CVE-2019-16780 medium priority: Ubuntu including 1 source packages (wordpress), 18 status rows across 18 suites (bionic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 12, ignored 2, needs-triage 2, DNE 1, released 1.	https://ubuntu.com/security/CVE-2019-16780

Affected software / configurations for CVE-2019-16780

Vendor	Product	Version	Raw CPE
wordpress	wordpress	> 3.7, < 5.3.1	cpe:2.3:a:wordpress:wordpress::::::::
wordpress	wordpress	3.7	cpe:2.3:a:wordpress:wordpress:3.7:-::::::
debian	debian_linux	9.0	cpe:2.3:o:debian:debian_linux:9.0:::::::*
debian	debian_linux	10.0	cpe:2.3:o:debian:debian_linux:10.0:::::::*

References for CVE-2019-16780

URL	Tags
https://github.com/WordPress/wordpress-develop/commit/505dd6a20b6fc3d06130018c1caeff764248c29e	Patch Third Party Advisory
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-x3wp-h3qx-9w94	Third Party Advisory
https://hackerone.com/reports/738644	Permissions Required Third Party Advisory
https://seclists.org/bugtraq/2020/Jan/8	Mailing List Third Party Advisory
https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/	Release Notes Third Party Advisory
https://wpvulndb.com/vulnerabilities/9976	Third Party Advisory
https://www.debian.org/security/2020/dsa-4599	Third Party Advisory
https://www.debian.org/security/2020/dsa-4677	Third Party Advisory

URL

CVE-2019-16780 | Stored cross-site scripting (XSS) in WordPress block editor

Exploit prediction scoring system (EPSS) score for CVE-2019-16780

Common vulnerability scoring system (CVSS) metrics for CVE-2019-16780

Weakness enumeration for CVE-2019-16780

OS Trackers for CVE-2019-16780

Affected software / configurations for CVE-2019-16780

References for CVE-2019-16780