# CVE-2026-102499: Modern Events Calendar (Lite & Pro) < 7.37.0 - Subscriber+ SQLi via mec_attendees AJAX Action


- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-rxf7-qp8j-cx93

## What is CVE-2026-102499?

CVE-2026-102499 is a high-severity vulnerability in Unknown Modern Event Calendar Pro, published on 21 Oct 2026. 

### Official description

The Modern Events Calendar Lite WordPress plugin before 7.37.0, Modern Event Calendar Pro WordPress plugin before 7.37.0 do not sanitise and escape a parameter before using it in a SQL statement, which allows authenticated users with Subscriber-level access and above to append additional SQL queries into already existing queries and extract sensitive data from the database.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-102499 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102499 is a high-severity vulnerability in Unknown Modern Event Calendar Pro, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-102499 in the wild and no public exploit code.

Affected product: Unknown Modern Event Calendar Pro. 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-102499/ (Markdown: https://insights.sbomify.com/CVE-2026-102499/index.md)
```

## Sources

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

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