Liquid Web The Events Calendar unauthenticated cross-site scripting via content injection
- Exploited
- No known exploitation
- Fix
- Fixed in 6.18.4.1
- Who is exposed
- Not reported
Summary
The Events Calendar plugin for WordPress, from Liquid Web / StellarWP, has a cross-site scripting flaw that lets an attacker inject script tags into web pages. An attacker can do this remotely over the network, without logging in and without any action from a user.
Written by a model
Original description
Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in Liquid Web / StellarWP The Events Calendar the-events-calendar allows Code Injection.This issue affects The Events Calendar: from n/a through 6.18.4.
What to do
Upgrade to a fixed version: 6.18.4.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131768 (WordPress The Events Calendar plugin <= 6.18.4 - Content Injection vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131768 (entry last updated 2026-11-20):
Affected:
- Liquid Web / StellarWP The Events Calendar: fixed in 6.18.4.1
Fixed versions: 6.18.4.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131768 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131768 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/the-events-calendar/vulnerability/wordpress-the-events-calendar-plugin-6-18-4-content-injection-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131768
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131768"}.Affected versions
- the-events-calendarfixed in 6.18.4.1 · through 6.18.4
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131768 |
| Record | NVD · CVE-2026-131768 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/the-events-calendar/vulnerability/wordpress-the-events-calendar-plugin-6-18-4-content-injection-vulnerability?_s_id=cve |
Questions about CVE-2026-131768
Is CVE-2026-131768 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-131768?
the-events-calendar: through 6.18.4 (fixed in 6.18.4.1).
Source: cve.now feed data
How do I fix CVE-2026-131768?
Upgrade to a fixed version: 6.18.4.1.
Source: cve.now feed data
Related
- CVE-2026-95606WordPress The Events Calendar plugin <= 6.17.4 - PHP Object Injection vulnerability
- CVE-2026-49772WordPress The Events Calendar plugin 6.15.12-6.16.2 - SQL Injection vulnerability
- CVE-2026-123464WordPress The Events Calendar plugin <= 6.18.3 - Cross Site Scripting (XSS) vulnerability
- CVE-2026-119369WordPress The Events Calendar plugin <= 6.18.2 - Cross Site Scripting (XSS) vulnerability
- CVE-2026-119370WordPress The Events Calendar plugin <= 6.18.2 - Cross Site Scripting (XSS) vulnerability
- CVE-2026-110903WordPress The Events Calendar plugin <= 6.18.1 - Cross Site Scripting (XSS) vulnerability
No corrections so far. Something wrong on this page? Report an error.