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

> Authenticated users can access other students' personal and financial records by manipulating the receipt ID parameter in the payment API.

- **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:** 4 Dec 2025
- **Updated:** 8 Dec 2025
- **Also known as:** GHSA-fp99-3rpw-vrxx

## What is CVE-2025-61148?

CVE-2025-61148 is a medium-severity missing authorization vulnerability in n/a, published on 4 Dec 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 in the EduplusCampus 3.0.1 Student Payment API allows authenticated users to access other students personal and financial records by modifying the 'rec_no' parameter in the /student/get-receipt endpoint.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Edupluscampus Edupluscampus.

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

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

## Is CVE-2025-61148 being exploited?

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

Public exploit code:

- The vulnerability exists in the Student Payment API. The application fails to properly validate whether the user requesting a receipt is authorized to view it. By modifying the rec_no parameter in the API request, an attacker can access the receipts of other users. (github_poc): https://github.com/sharma19d/CVE-2025-61148

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61148 is a medium-severity missing authorization vulnerability in n/a, published on 4 Dec 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-61148 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-61148/ (Markdown: https://insights.sbomify.com/CVE-2025-61148/index.md)
```

## Sources

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

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