SQL injection via unsanitized hyname parameter
Published Jan 13, 2025 · Updated Jan 13, 2025
SQL injection in liujianview gymxmjpa 1.0 allows remote authenticated users to read or modify database data via hyname. EquipmentDaoImpl in src/main/java/com/liujian/gymxmjpa/controller/EquipmentController.java uses the attacker-controlled hyname value in a SQL operation without neutralizing it. A valid account is required; exploitation is limited to the application's database privileges and can affect stored data or database availability.
Summary
What happened
SQL injection in liujianview gymxmjpa 1.0 allows remote authenticated users to read or modify database data via hyname. EquipmentDaoImpl in src/main/java/com/liujian/gymxmjpa/controller/EquipmentController.java uses the attacker-controlled hyname value in a SQL operation without neutralizing it. A valid account is required; exploitation is limited to the application's database privileges and can affect stored data or database availability.
The record
- CVE
- CVE-2025-0407
- Published
- Jan 13, 2025
- Updated
- Jan 13, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-74, CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 13, 2025CVE publishedPublication date reported by the CVE source.
- Jan 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue #7 proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo