The Yoast SEO plugin before 11.6-RC5 for WordPress does not properly restrict unfiltered HTML in term descriptions.

published 2019-07-09 7y ago modified 2026-06-17 4mo ago also EUVD-2019-4946

cvss: 9.9; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 3.3%; EPSS 3.3% chance of exploitation in 30 days, percentile 88%
public exploits: 0; none known

Patch / fix

fixed in 1 links 1

yoast yoast_seo 11.6

github.com/Yoast/wordpress-seo/releases/tag/11.6-RC5 release

Is CVE-2019-13478 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

3.30% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	9.9	CVSS:3.0/AC:L/AV:N/A:L/C:H/I:H/PR:L/S:C/UI:N
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA	3.0	9.9	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

Technology feeds

WordPress rss critical rss

References

github.com /Yoast/wordpress-seo/releases/tag/11.6-RC5
release-notes
wpvulndb.com /vulnerabilities/9445
third-party-advisory

Sources

CVE List CVE-2019-13478
NVD CVE-2019-13478

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.