CVE-2019-16218
published 2019-09-11CVE-2019-16218: WordPress before 5.2.3 allows XSS in stored comments.
PriorityP428medium6.1CVSS 3.1
AVNACLPRNUIRSCCLILAN
EPSS
1.81%
76.1th percentile
WordPress before 5.2.3 allows XSS in stored comments.
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | wordpress | < wordpress 5.2.3+dfsg1-1 (bookworm) | wordpress 5.2.3+dfsg1-1 (bookworm) |
| wordpress | wordpress | < 5.2.3 | 5.2.3 |
| wordpress | wordpress | >= 0 < 5.2.3+dfsg1-1 | 5.2.3+dfsg1-1 |
| wordpress | wordpress | >= 0 < 5.2.3+dfsg1-1 | 5.2.3+dfsg1-1 |
| wordpress | wordpress | >= 0 < 5.2.3+dfsg1-1 | 5.2.3+dfsg1-1 |
| wordpress | wordpress | >= 0 < 5.2.3+dfsg1-1 | 5.2.3+dfsg1-1 |
CVSS provenance
nvdv3.16.1MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:P/A:N
osv6.1MEDIUM
vendor_debian6.1MEDIUM
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.
GHSA
GHSA-v5hr-6h2c-gx45: WordPress before 5
ghsa_unreviewed·2022-05-24
CVE-2019-16218 [MEDIUM] CWE-79 GHSA-v5hr-6h2c-gx45: WordPress before 5
WordPress before 5.2.3 allows XSS in stored comments.
OSV
CVE-2019-16218: WordPress before 5
osv·2019-09-11·CVSS 6.1
CVE-2019-16218 [MEDIUM] CVE-2019-16218: WordPress before 5
WordPress before 5.2.3 allows XSS in stored comments.
Debian
CVE-2019-16218: wordpress - WordPress before 5.2.3 allows XSS in stored comments.
vendor_debian·2019·CVSS 6.1
CVE-2019-16218 [MEDIUM] CVE-2019-16218: wordpress - WordPress before 5.2.3 allows XSS in stored comments.
WordPress before 5.2.3 allows XSS in stored comments.
Scope: local
bookworm: resolved (fixed in 5.2.3+dfsg1-1)
bullseye: resolved (fixed in 5.2.3+dfsg1-1)
forky: resolved (fixed in 5.2.3+dfsg1-1)
sid: resolved (fixed in 5.2.3+dfsg1-1)
trixie: resolved (fixed in 5.2.3+dfsg1-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-16218 wordpress: XSS in stored comments [epel-7]
bugzilla·2019-11-25·CVSS 6.1
CVE-2019-16218 [MEDIUM] CVE-2019-16218 wordpress: XSS in stored comments [epel-7]
CVE-2019-16218 wordpress: XSS in stored comments [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' request t
Bugzilla
CVE-2019-16218 wordpress: XSS in stored comments
bugzilla·2019-11-25·CVSS 6.1
CVE-2019-16218 [MEDIUM] CVE-2019-16218 wordpress: XSS in stored comments
CVE-2019-16218 wordpress: XSS in stored comments
WordPress before 5.2.3 allows XSS in stored comments.
Reference:
https://wpvulndb.com/vulnerabilities/9861
Discussion:
Created wordpress tracking bugs for this issue:
Affects: epel-6 [bug 1776430]
Affects: epel-7 [bug 1776431]
---
Fixed in 5.2.4
Bugzilla
CVE-2019-16218 wordpress: XSS in stored comments [epel-6]
bugzilla·2019-11-25·CVSS 6.1
CVE-2019-16218 [MEDIUM] CVE-2019-16218 wordpress: XSS in stored comments [epel-6]
CVE-2019-16218 wordpress: XSS in stored comments [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' request t
https://lists.debian.org/debian-lts-announce/2019/10/msg00023.htmlhttps://seclists.org/bugtraq/2020/Jan/8https://wordpress.org/news/2019/09/wordpress-5-2-3-security-and-maintenance-release/https://wpvulndb.com/vulnerabilities/9861https://www.debian.org/security/2020/dsa-4599https://www.debian.org/security/2020/dsa-4677https://lists.debian.org/debian-lts-announce/2019/10/msg00023.htmlhttps://seclists.org/bugtraq/2020/Jan/8https://wordpress.org/news/2019/09/wordpress-5-2-3-security-and-maintenance-release/https://wpvulndb.com/vulnerabilities/9861https://www.debian.org/security/2020/dsa-4599https://www.debian.org/security/2020/dsa-4677
2019-09-11
Published