The Events CalendarWordPress extension · Stellarwp
CVE-2019-15109
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe the-events-calendar plugin before 4.8.2 for WordPress has XSS via the tribe_paged URL parameter.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA reflected cross-site scripting (XSS) vulnerability exists in the-events-calendar WordPress plugin versions before 4.8.2. The tribe_paged URL parameter is not properly sanitized, allowing attackers to inject malicious JavaScript that executes in victims' browsers when they visit crafted URLs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
The Events CalendarWordPress extension
< 4.8.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify The Events Calendar plugin is installedLog into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'The Events Calendar' by Stellarwp in the list. Alternatively, check the file system at wp-content/plugins/the-events-calendar/ for the plugin directory.Affected if The plugin is installed and active
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and click on the plugin name to view details, or inspect the plugin header in wp-content/plugins/the-events-calendar/the-events-calendar.php for the 'Version' comment. You can also check the readme.txt file in the plugin directory.Affected if Version cannot be determined or is below 4.8.2
-
Compare version against affected rangeCompare the installed version number to 4.8.2. Any version below 4.8.2 (such as 4.8.1, 4.8.0, 4.7.x, etc.) is in the affected range.Affected if Installed version is less than 4.8.2 (e.g., 4.8.1, 4.7.4, etc.)
-
Test for vulnerable parameter exposureVisit a page on the site with the query parameter tribe_paged=<script>alert(1)</script> appended to the URL (e.g., example.com/events?tribe_paged=<script>alert(1)</script>). Use browser developer tools or view page source to check if the parameter value is reflected unescaped in the HTML.Affected if The parameter value appears literally in the page HTML without HTML encoding (script tags are not escaped)
You are affected if The Events Calendar plugin is installed with a version number lower than 4.8.2 and the tribe_paged URL parameter reflects user input without sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data4.8.2
Upgrade the-events-calendar plugin to version 4.8.2 or later to receive the patch. Until patched, avoid clicking untrusted links referencing the tribe_paged parameter.
Fix this in The Events Calendar
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15109 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-15109 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data