# CVE-2025-4136: Weitong Mall Sale Endpoint improper authorization

> Remote attackers can bypass authorization checks on the Sale Endpoint to access or modify data without proper permissions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **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:** 30 Apr 2025
- **Updated:** 1 May 2025
- **Also known as:** GHSA-pfvg-rvxx-jfrg

## What is CVE-2025-4136?

CVE-2025-4136 is a medium-severity missing authorization vulnerability in Weitong Mall, published on 30 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Weitong Mall 1.0.0. It has been classified as critical. This affects an unknown part of the component Sale Endpoint. The manipulation of the argument ID leads to improper authorization. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2025-4136?


## How do I fix CVE-2025-4136?

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

## Is CVE-2025-4136 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4136 and fix it if it is affected.

What it is: CVE-2025-4136 is a medium-severity missing authorization vulnerability in Weitong Mall, published on 30 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4136 in the wild and no public exploit code.

Affected product: Weitong 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-2025-4136/ (Markdown: https://insights.sbomify.com/CVE-2025-4136/index.md)
```

## Sources

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

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