YiShaAdmin sql injection in pagination sorting component
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
A SQL injection flaw in the Pagination Sorting component of liukuo362573 YiShaAdmin lets an attacker manipulate the sort argument to inject SQL into database queries. An attacker can reach it remotely over the network with a low-privileged login, and successful exploitation can expose or alter stored database data.
Written by a model
Original description
A vulnerability was detected in liukuo362573 YiShaAdmin up to ba04d5072885447553e372bb87e372b55a90780c. Impacted is the function SqlServerPageSql/OraclePageSql/MySqlPageSql/ of the file YiSha.Data/YiSha.Data/Extension/DatabasePageExtension.cs of the component Pagination Sorting. The manipulation of the argument sort results in sql injection. It is possible to launch the attack remotely. The exploit is now public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The patch is identified as 19b0bdffc9587bff291bac81586953277abe5b84. Applying a patch is advised to resolve this issue.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134009 (liukuo362573 YiShaAdmin Pagination Sorting DatabasePageExtension.cs sql injection), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134009 (entry last updated 2026-11-21):
Affected:
- liukuo362573 YiShaAdmin: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-134009 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134009 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/liukuo362573/YiShaAdmin/commit/19b0bdffc9587bff291bac81586953277abe5b84
- https://vuldb.com/vuln/441601
- https://vuldb.com/vuln/441601/cti
- https://vuldb.com/cve/CVE-2026-134009
- https://vuldb.com/submit/1052136
- https://github.com/liukuo362573/YiShaAdmin/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134009
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134009"}.Affected versions
- liukuo362573 YiShaAdminVersion range not reported
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134009 |
| Record | NVD · CVE-2026-134009 |
| Other links 6 | |
| Advisory | VulDB · Advisory #441601 |
| Advisory | VulDB · Threat intelligence #441601 |
| Advisory | VulDB · CVE-2026-134009 record |
| Advisory | VulDB · Submission #1052136 |
| Patch | GitHub · liukuo362573/YiShaAdmin · Commit 19b0bdff |
| Repository | GitHub · liukuo362573/YiShaAdmin · Repository |
Related
- CVE-2022-51022YiShaAdmin 3.1 Unauthenticated Path Traversal via DownloadFile endpoint
- CVE-2026-129175U.S Department of the Interior Unstable Slope Management Program unauthenticated SQL Injection
- CVE-2026-134293SurrealDB 3.1.0 before 4.0.0 SQL Injection via MCP Tool Identifier Escaped Backticks
- CVE-2026-131701WordPress WP Media folder plugin <= 6.2.8 - SQL Injection vulnerability
- CVE-2026-131705WordPress ProfileGrid plugin <= 6.0.0.6 - SQL Injection vulnerability
- CVE-2026-134372Frappe ERPNext 4.3.0 before 15.121.6 SQL Injection in Selling and Buying Modules
No corrections so far. Something wrong on this page? Report an error.