# CVE-2026-119655: CoreShop through 1.5.5 SQL Injection via order Parameter in GetGoodsPageList


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-394c-r5mr-6r95

## What is CVE-2026-119655?

CVE-2026-119655 is a high-severity vulnerability in CoreUnion CoreShop, published on 30 Oct 2026. 

### Official description

CoreShop through 1.5.5 contains an unauthenticated sql injection vulnerability in the api/Good/GetGoodsPageList endpoint via the unvalidated order parameter appended to ORDER BY. Attackers can inject subqueries that bypass SqlSugar's field check and use boolean-based or time-based blind techniques to extract member accounts and orders.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-119655?


## How do I fix CVE-2026-119655?

No fix has been published for CVE-2026-119655 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119655 being exploited?

There is no known exploitation of CVE-2026-119655 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119655 and fix it if it is affected.

What it is: CVE-2026-119655 is a high-severity vulnerability in CoreUnion CoreShop, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119655 in the wild and no public exploit code.

Affected product: CoreUnion CoreShop. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119655/ (Markdown: https://insights.sbomify.com/CVE-2026-119655/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119655
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119655
- OSV: https://osv.dev/vulnerability/CVE-2026-119655

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119655/
Summaries are generated and may contain mistakes; the official description above is the record.