# CVE-2026-79406: macrozheng mall quantity OmsCartItemServiceImpl.updateQuantity logic error

> Attackers can manipulate cart item quantities via the updateQuantity function, leading to business logic errors in the macrozheng mall application.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-jvqx-hg2g-crvf

## What is CVE-2026-79406?

CVE-2026-79406 is a medium-severity vulnerability in macrozheng mall, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in macrozheng mall up to 1.0.3. Affected is the function OmsCartItemServiceImpl.updateQuantity of the file /cart/update/quantity. The manipulation of the argument quantity leads to business logic errors. The attack may be initiated remotely. The vendor deleted the GitHub issue for this vulnerability without any explanation.

Weakness: CWE-840

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


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

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

## Is CVE-2026-79406 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79406 is a medium-severity vulnerability in macrozheng mall, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-79406 in the wild and no public exploit code.

Affected product: macrozheng mall. 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-79406/ (Markdown: https://insights.sbomify.com/CVE-2026-79406/index.md)
```

## Sources

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

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