# CVE-2026-29909: Missing authorization in n/a

> Unauthenticated attackers can enumerate server directory contents via the file management module, exposing sensitive file structures.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-72gm-vcvr-mjgq

## What is CVE-2026-29909?

CVE-2026-29909 is a medium-severity missing authorization vulnerability in n/a, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MRCMS V3.1.2 contains an unauthenticated directory enumeration vulnerability in the file management module. The /admin/file/list.do endpoint lacks authentication controls and proper input validation, allowing remote attackers to enumerate directory contents on the server without any credentials.

Weakness: CWE-425 (Direct Request), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Mrcms Mrcms.

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

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

## Is CVE-2026-29909 being exploited?

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

Public exploit code:

- MRCMS V3.1.2 contains an unauthenticated directory enumeration vulnerability in the file management module. The `/admin/file/list.do` endpoint lacks authentication controls and proper input validation, allowing remote attackers to enumerate directory contents on the server without any credentials. (github_poc): https://github.com/qflksheep/CVE-2026-29909-MRCMS-vulnerability

## Other vulnerabilities in n/a

- [CVE-2026-31272](https://insights.sbomify.com/CVE-2026-31272/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-48177](https://insights.sbomify.com/CVE-2024-48177/): SQL injection in n/a (high 8.8)
- [CVE-2024-24161](https://insights.sbomify.com/CVE-2024-24161/): Path traversal in n/a (high 7.5)
- [CVE-2024-25428](https://insights.sbomify.com/CVE-2024-25428/): SQL injection in n/a (medium 6.5)
- [CVE-2024-24160](https://insights.sbomify.com/CVE-2024-24160/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-29909 is a medium-severity missing authorization vulnerability in n/a, published on 30 Mar 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-29909 exists.

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

## Sources

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

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