# CVE-2026-87927: MaxSite CMS through 109.6 Local File Inclusion via ajax dispatcher

> Unauthenticated attackers can execute privileged handler files via path traversal in MaxSite CMS dispatchers, leading to code execution and privilege escalation.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-wxg4-xmxc-6qm6

## What is CVE-2026-87927?

CVE-2026-87927 is a high-severity path traversal vulnerability in MaxSite CMS, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MaxSite CMS through 109.6 contains a local file inclusion vulnerability in the ajax and require-maxsite dispatchers that allows unauthenticated attackers to execute privileged handler files by supplying base64-encoded path traversal sequences. Attackers can bypass path validation checks and execute admin-gated handler actions without authentication to access sensitive functionality.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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


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

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

## Is CVE-2026-87927 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87927 is a high-severity path traversal vulnerability in MaxSite CMS, published on 9 Sep 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-87927 exists.

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

## Sources

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

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