CVE-2025-0404
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 · uneditedA vulnerability has been found in liujianview gymxmjpa 1.0 and classified as critical. This vulnerability affects the function CoachController of the file src/main/java/com/liujian/gymxmjpa/controller/CoachController.java. The manipulation of the argument coachName leads to sql injection. The attack can 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 · moderate confidenceSQL injection vulnerability in the CoachController of liujianview gymxmjpa 1.0 allows remote attackers to inject malicious SQL queries through the coachName parameter. The vulnerable code uses unsanitized user input directly in SQL queries instead of parameterized statements.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm gymxmjpa versionLocate the deployed gymxmjpa application and identify its version. Check WAR file, manifest files, or application metadata for version 1.0.Affected if The installed version is gymxmjpa 1.0.
-
Locate CoachController classFind the CoachController.java file in the deployed application source code or decompiled classes. Search for a controller handling coach-related endpoints.Affected if The CoachController class exists and handles requests.
-
Inspect SQL query construction for coachNameOpen CoachController and search for SQL query strings that incorporate the coachName parameter. Look for statements using String concatenation, + operator, or string formatting in WHERE clauses.Affected if SQL queries concatenate the coachName parameter directly into query strings.
-
Verify parameterization is not usedExamine whether the SQL queries use PreparedStatement with parameter placeholders (?) or parameterized methods. Check if the code uses createStatement() instead of prepareStatement().Affected if The coachName parameter is passed directly into SQL without prepared statement parameter binding.
-
Test coachName endpoint for injectionIf the coachName parameter is exposed via HTTP request, send a test payload such as ' OR '1'='1 to the relevant endpoint and observe if unexpected data is returned or if the query behaves differently than expected.Affected if The endpoint returns unexpected results or behaves inconsistently with the test payload, indicating SQL injection is possible.
If gymxmjpa version 1.0 is running and the CoachController uses direct string concatenation for the coachName parameter in SQL queries without PreparedStatement, the environment is affected by CVE-2025-0404.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace string concatenation in SQL queries with parameterized queries (PreparedStatement) and implement input validation for the coachName parameter. Apply least-privilege database access to limit impact of any successful injection.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0404 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0404 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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