CVE-2026-7060
SQL Injection in liyupi yu-picture MyBatis-Plus Component
Publication date: 2026-04-26
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| liyupi | yu-picture | to a053632c41340152bf75b66b3c543d129123d8ec (inc) |
| mybatis | mybatis-plus | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the liyupi yu-picture project, specifically in the PageRequest function of the PictureServiceImpl.java file within the MyBatis-Plus component. It involves improper handling of the argument 'sortField', which can be manipulated to perform an SQL injection attack. This means an attacker can remotely execute malicious SQL commands by exploiting this flaw.
How can this vulnerability impact me? :
The vulnerability allows remote attackers to perform SQL injection, which can lead to unauthorized access, data leakage, data modification, or deletion within the affected application. This can compromise the integrity, confidentiality, and availability of the data managed by the application.
What immediate steps should I take to mitigate this vulnerability?
Applying a patch is advised to resolve this issue.
Since the project has not reacted yet and does not use versioning, monitoring for updates or patches from the maintainers is important.