# CVE-2025-4494: JAdmin-JAVA JAdmin Admin Backend NoNeedLoginController.java toLogin improper authentication

> Remote attackers can bypass authentication in the JAdmin admin backend to gain unauthorized access and privileges.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2025
- **Updated:** 10 May 2025
- **Also known as:** GHSA-4374-q6w2-q795

## What is CVE-2025-4494?

CVE-2025-4494 is a medium-severity authentication bypass vulnerability in JAdmin-JAVA JAdmin, published on 9 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in JAdmin-JAVA JAdmin 1.0. Affected is the function toLogin of the file NoNeedLoginController.java of the component Admin Backend. The manipulation leads to improper authentication. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Jadmin-Java Jadmin.

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

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

## Is CVE-2025-4494 being exploited?

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

## Other vulnerabilities in JAdmin-JAVA JAdmin

- [CVE-2025-4495](https://insights.sbomify.com/CVE-2025-4495/): JAdmin-JAVA JAdmin save cross site scripting (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4494 is a medium-severity authentication bypass vulnerability in JAdmin-JAVA JAdmin, published on 9 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4494 in the wild and no public exploit code.

Affected product: JAdmin-JAVA JAdmin. 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-4494/ (Markdown: https://insights.sbomify.com/CVE-2025-4494/index.md)
```

## Sources

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

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