# CVE-2025-6749: huija bicycleSharingServer AdminController.java searchAdminMessageShow sql injection

> Remote attackers can exploit SQL injection in the admin message search function to read or modify database contents.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 27 Jun 2025
- **Updated:** 27 Jun 2025
- **Also known as:** GHSA-h3hh-chqj-5w9f

## What is CVE-2025-6749?

CVE-2025-6749 is a medium-severity SQL injection vulnerability in huija bicycleSharingServer, published on 27 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as critical was found in huija bicycleSharingServer up to 7b8a3ba48ad618604abd4797d2e7cf3b5ac7625a. Affected by this vulnerability is the function searchAdminMessageShow of the file AdminController.java. The manipulation of the argument Title leads to sql injection. The attack can be launched 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2025-6749 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6749 is a medium-severity SQL injection vulnerability in huija bicycleSharingServer, published on 27 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6749 exists.

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

## Sources

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

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