# CVE-2026-112027 — light0011 cms

> As of 2026-10-19, CVE-2026-112027 is a MEDIUM-severity vulnerability in light0011 cms, CVSS v3.1 5.3, EPSS 0.3% (25.4th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-112027 as of 2026-10-19; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-19

## What is CVE-2026-112027?

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.

The record classifies CVE-2026-112027 under weakness classes [CWE-538](https://cwe.mitre.org/data/definitions/538.html), [CWE-200](https://intel.threadlinqs.com/cwe/CWE-200). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 32 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 5.3 — MEDIUM (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:C`)
- **CVSS v4.0 base score:** 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`)
- **EPSS (FIRST):** 0.3% probability of exploitation in the next 30 days, higher than 25.4% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-18

## Is CVE-2026-112027 being exploited?

It currently carries a trending score of 36 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **light0011**: cms

## How to fix CVE-2026-112027

No vendor patch reference has been recorded for CVE-2026-112027 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-112027

No threat campaign in the Threadlinqs corpus currently references CVE-2026-112027, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, GitHub Security Advisories, FIRST EPSS.

**Exploit and proof of concept**

- [github.com — exploit](https://github.com/light0011/cms/issues/15)

**Technical analysis**

- [vuldb.com — vdb entry](https://vuldb.com/vuln/421675)

**Third-party advisory**

- [vuldb.com — signature](https://vuldb.com/vuln/421675/cti)
- [vuldb.com — third party advisory](https://vuldb.com/cve/CVE-2026-112027)
- [vuldb.com — third party advisory (1008072)](https://vuldb.com/submit/1008072)

**Issue tracking and product pages**

- [github.com — product](https://github.com/light0011/cms/)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-112027
No Threadlinqs detection currently covers CVE-2026-112027; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
