# CVE-2026-108799: jackq XCMS Password Recovery Mail Endpoint PublicController.class.php sendFindPwdMail sql injection

> Attackers can exploit SQL injection in the password recovery email endpoint to read or modify database contents.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-prc4-c7gg-w62j

## What is CVE-2026-108799?

CVE-2026-108799 is a medium-severity SQL injection vulnerability in jackq XCMS, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in jackq XCMS up to 3fab5342cc509945a7ce1b8ec39d19f701b89261. Impacted is the function PublicController::sendFindPwdMail of the file Admin/Home/Controller/PublicController.class.php of the component Password Recovery Mail Endpoint. This manipulation of the argument email causes sql injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-108799 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108799 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108799 is a medium-severity SQL injection vulnerability in jackq XCMS, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108799 exists.

Affected product: jackq XCMS. 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-108799/ (Markdown: https://insights.sbomify.com/CVE-2026-108799/index.md)
```

## Sources

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

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