# CVE-2026-108811: WMCMS index.php information disclosure

> Remote attackers can exploit a flaw in WMCMS index.php to disclose sensitive information via the path/file argument.

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

## What is CVE-2026-108811?

CVE-2026-108811 is a medium-severity vulnerability in WMCMS, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in WMCMS 4.446.1257. The affected element is an unknown function of the file /index.php. This manipulation of the argument path/file causes information disclosure. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-108811 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108811 is a medium-severity vulnerability in WMCMS, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108811 exists.

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

## Sources

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

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