# CVE-2026-112027: light0011 cms Uploadify check-exists.php file_exists file information disclosure

> Remote attackers can exploit the Uploadify component in light0011 CMS to disclose file and directory information via the check-exists.php script.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-387w-mphj-m93q

## What is CVE-2026-112027?

CVE-2026-112027 is a medium-severity vulnerability in light0011 cms, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was detected in light0011 cms c774dce31c6df0055568a8d5c53d964d99be199d/f72cf46f601efb2a0618c3814cc2f61380b38930. Affected by this vulnerability is the function file_exists of the file Public/Home/js/uploadify/check-exists.php of the component Uploadify. The manipulation of the argument filename results in file and directory information exposure. The attack may be launched remotely. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-112027 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112027 is a medium-severity vulnerability in light0011 cms, published on 18 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-112027 exists.

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

## Sources

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

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