# CVE-2026-14953: Missing authorization in FDS 102

> A low-privileged remote attacker can enumerate all users and identify privileged accounts via an unprotected API endpoint in Frauscher FDS 102 systems.

- **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`)
- **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:** 20 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-cv6m-pghp-xm7f

## What is CVE-2026-14953?

CVE-2026-14953 is a medium-severity missing authorization vulnerability in Frauscher Sensortechnik FDS 102, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A low-privileged remote attacker can enumerate all configured users and identify which accounts hold elevated privileges using the endpoint /api/user/fetch-all.php.

Weakness: CWE-425 (Direct Request)

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


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

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

## Is CVE-2026-14953 being exploited?

There is no known exploitation of CVE-2026-14953 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14953 is a medium-severity missing authorization vulnerability in Frauscher Sensortechnik FDS 102, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14953 in the wild and no public exploit code.

Affected product: Frauscher Sensortechnik FDS 102. 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-14953/ (Markdown: https://insights.sbomify.com/CVE-2026-14953/index.md)
```

## Sources

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

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