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

> Attackers can bypass client-side authorization checks to access administrative features and execute privileged functions in mJobtime.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-fqx2-pf77-2r9j

## What is CVE-2025-51682?

CVE-2025-51682 is a critical missing authorization vulnerability in n/a, published on 1 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mJobtime 15.7.2 handles authorization on the client side, which allows an attacker to modify the client-side code and gain access to administrative features. Additionally, they can craft requests based on the client-side code to call these administrative functions directly.

Weakness: CWE-602 (Client-Side Enforcement of Server-Side Security)

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

It affects 1 product.


Products: Mjobtime Mjobtime.

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

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

## Is CVE-2025-51682 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-51683](https://insights.sbomify.com/CVE-2025-51683/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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