dbcve.org
InjectionWeakness · CWE-74

CVE-2025-6753

MEDIUM · 6.3 CVSS v3.1 Published 2025-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in huija bicycleSharingServer 1.0 and classified as critical. This issue affects the function selectAdminByNameLike of the file AdminController.java. The manipulation leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The vulnerability exists in the selectAdminByNameLike function within AdminController.java of the huija bicycleSharingServer 1.0 application. User-supplied input is directly concatenated into SQL queries without proper parameterization or sanitization, allowing an attacker to inject malicious SQL statements. This can lead to unauthorized database access, data exfiltration, or potential remote code execution depending on database configuration.

MitigationReplace dynamic SQL string concatenation with parameterized queries (PreparedStatement) in the selectAdminByNameLike function, apply input validation on all user-supplied parameters, and audit similar functions throughout the codebase for additional SQL injection vulnerabilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the application version
    Locate the application deployment files or build artifacts for bicycleSharingServer and check the version manifest, pom.xml, or build.properties to confirm version 1.0 is deployed
    Affected if The installed version is huija bicycleSharingServer 1.0
  2. Locate the vulnerable source file
    Search the codebase for AdminController.java and verify the selectAdminByNameLike function exists within it
    Affected if The file AdminController.java with the selectAdminByNameLike function is present in the deployment
  3. Inspect the SQL query implementation
    Open AdminController.java and locate the selectAdminByNameLike method. Examine whether user input is concatenated directly into the SQL string (e.g., 'SELECT * FROM ... WHERE name LIKE ' + userInput) rather than using parameterized queries
    Affected if The code shows direct string concatenation of user-supplied parameters into the SQL query without PreparedStatement or parameter binding
  4. Confirm admin functionality is exposed
    Check the application routing or endpoint configuration to determine if the selectAdminByNameLike function is accessible via an HTTP API endpoint (such as /admin/search or similar)
    Affected if The vulnerable function is exposed through a reachable HTTP endpoint that accepts user input
  5. Verify database connectivity
    Examine the database configuration file (application.properties, application.yml, or similar) to confirm the application connects to a database that accepts SQL queries
    Affected if The application is configured with active database connectivity that can process the injected SQL statements

You are affected if you are running huija bicycleSharingServer version 1.0 with the selectAdminByNameLike function present and accessible, and the source code shows direct SQL string concatenation instead of parameterized queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL string concatenation with parameterized queries (PreparedStatement) in the selectAdminByNameLike function, apply input validation on all user-supplied parameters, and audit similar functions throughout the codebase for additional SQL injection vulnerabilities.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6753 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6753 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data