The the-events-calendar plugin before 4.8.2 for WordPress has XSS via the tribe_paged URL parameter.

published 2019-08-21 7y ago modified 2026-06-17 4mo ago also EUVD-2019-6180

cvss: 6.1; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 64%
public exploits: 0; none known

Patch / fix

fixed in 1

stellarwp the_events_calendar 4.8.2

Is CVE-2019-15109 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

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

CVSS scores

assigned by	version	score	vector
NVD	3.0	6.1	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

Technology feeds

WordPress rss critical rss

References

wordpress.org /plugins/the-events-calendar/#developers
release-notes
wpvulndb.com /vulnerabilities/9554
third-party-advisory

Sources

CVE List CVE-2019-15109
NVD CVE-2019-15109

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.