# CVE-2026-114260: oretnom23 file-management-system-php AJAX ajax.php delete_folder missing authentication


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-v43j-3mh6-2hx8

## What is CVE-2026-114260?

CVE-2026-114260 is a medium-severity vulnerability in oretnom23 file-management-system-php, published on 21 Oct 2026. 

### Official description

A vulnerability has been found in oretnom23 file-management-system-php up to 2e3c1ebe60f121e8df4fb3f544f0e9591d9a01e4. This vulnerability affects the function delete_folder of the file ajax.php of the component AJAX Handler. The manipulation of the argument ID leads to missing authentication. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-114260 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114260 is a medium-severity vulnerability in oretnom23 file-management-system-php, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114260 exists.

Affected product: oretnom23 file-management-system-php. 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-114260/ (Markdown: https://insights.sbomify.com/CVE-2026-114260/index.md)
```

## Sources

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

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