# CVE-2026-114407: e107 CMS before 2.3.13 Reflected XSS via search.php author Parameter


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-26h5-jjjv-6774, GHSA-g7rc-4jvq-27m9

## What is CVE-2026-114407?

CVE-2026-114407 is a medium-severity vulnerability in e107inc e107, published on 21 Oct 2026. 

### Official description

e107 CMS before 2.3.13 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject malicious HTML by manipulating the author GET parameter in search.php, which is parsed with parse_str() and concatenated unescaped into a rendered input tag via the form handler's 'other' option key. Attackers can craft a single GET request containing a crafted author parameter to break out of the HTML input tag and inject an img element with an onerror handler, executing arbitrary JavaScript in the victim's browser session.

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

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


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

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

## Is CVE-2026-114407 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114407 is a medium-severity vulnerability in e107inc e107, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114407 in the wild and no public exploit code.

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

## Sources

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

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