# CVE-2025-55886: Missing authorization in n/a

> An authenticated attacker can manipulate the fe_uid parameter to access other users' payment history without authorization.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A: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:** 22 Sep 2025
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-px76-r7pq-gc82

## What is CVE-2025-55886?

CVE-2025-55886 is a medium-severity missing authorization vulnerability in n/a, published on 22 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Insecure Direct Object Reference (IDOR) vulnerability was discovered in ARD. The flaw exists in the `fe_uid` parameter of the payment history API endpoint. An authenticated attacker can manipulate this parameter to access the payment history of other users without authorization.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2025-55886?


## How do I fix CVE-2025-55886?

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

## Is CVE-2025-55886 being exploited?

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

Public exploit code:

- https://github.com/0xZeroSec/CVE-2025-55886 (github_poc): https://github.com/0xZeroSec/CVE-2025-55886

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-55886 and fix it if it is affected.

What it is: CVE-2025-55886 is a medium-severity missing authorization vulnerability in n/a, published on 22 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-55886 in the wild and no public exploit code.

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-2025-55886/ (Markdown: https://insights.sbomify.com/CVE-2025-55886/index.md)
```

## Sources

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

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