# CVE-2026-1649: Community Events <= 1.5.7 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'ce_venue_name' Parameter

> Administrators can inject arbitrary scripts via the venue name parameter, leading to stored XSS execution for other users.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-cxr2-7xvc-hh42

## What is CVE-2026-1649?

CVE-2026-1649 is a medium-severity cross-site scripting vulnerability in jackdewey Community Events, published on 18 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Community Events plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'ce_venue_name' parameter in all versions up to, and including, 1.5.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-1649?


## How do I fix CVE-2026-1649?

No fix has been published for CVE-2026-1649 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1649 being exploited?

There is no known exploitation of CVE-2026-1649 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1649 and fix it if it is affected.

What it is: CVE-2026-1649 is a medium-severity cross-site scripting vulnerability in jackdewey Community Events, published on 18 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1649 in the wild and no public exploit code.

Affected product: jackdewey Community Events. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1649/ (Markdown: https://insights.sbomify.com/CVE-2026-1649/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1649
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1649
- OSV: https://osv.dev/vulnerability/CVE-2026-1649

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1649/
Summaries are generated and may contain mistakes; the official description above is the record.