# CVE-2025-2322: 274056675 springboot-openai-chatgpt OpenController.java hard-coded credentials

> Hard-coded credentials in the OpenController allow remote attackers to gain unauthorized access to the Spring Boot ChatGPT application.

- **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:** 15 Mar 2025
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-qc7f-pxqv-xfrh

## What is CVE-2025-2322?

CVE-2025-2322 is a medium-severity vulnerability in 274056675 springboot-openai-chatgpt, published on 15 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in 274056675 springboot-openai-chatgpt e84f6f5. It has been classified as critical. This affects an unknown part of the file /chatgpt-boot/src/main/java/org/springblade/modules/mjkj/controller/OpenController.java. The manipulation leads to hard-coded credentials. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

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

It affects 1 product.


Products: 274056675 Springboot-Openai-Chatgpt.

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

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

## Is CVE-2025-2322 being exploited?

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

## Other vulnerabilities in 274056675 springboot-openai-chatgpt

- [CVE-2025-2320](https://insights.sbomify.com/CVE-2025-2320/): 274056675 springboot-openai-chatgpt User submit improper authorization (medium 6.9)
- [CVE-2025-2321](https://insights.sbomify.com/CVE-2025-2321/): 274056675 springboot-openai-chatgpt addData logic error (medium 5.3)
- [CVE-2025-2323](https://insights.sbomify.com/CVE-2025-2323/): 274056675 springboot-openai-chatgpt Number of Question questionCou updateQuestionCou behavioral workflow (medium 5.3)
- [CVE-2025-2334](https://insights.sbomify.com/CVE-2025-2334/): 274056675 springboot-openai-chatgpt Chat History chat deleteChat access control (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2322 is a medium-severity vulnerability in 274056675 springboot-openai-chatgpt, published on 15 Mar 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-2322 exists.

Affected product: 274056675 springboot-openai-chatgpt. 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-2322/ (Markdown: https://insights.sbomify.com/CVE-2025-2322/index.md)
```

## Sources

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

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