# CVE-2025-6702: linlinjava litemall post improper authorization

> Attackers can bypass authorization checks in the comment posting feature to 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:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 26 Jun 2025
- **Updated:** 27 Jun 2025
- **Also known as:** GHSA-jcg7-h3pf-wrm2

## What is CVE-2025-6702?

CVE-2025-6702 is a medium-severity missing authorization vulnerability in linlinjava litemall, published on 26 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, was found in linlinjava litemall 1.8.0. Affected is an unknown function of the file /wx/comment/post. The manipulation of the argument adminComment leads to improper authorization. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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

It affects 1 product.


Products: Linlinjava Litemall.

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

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

## Is CVE-2025-6702 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6702 exists.

## Other vulnerabilities in linlinjava litemall

- [CVE-2018-18434](https://insights.sbomify.com/CVE-2018-18434/): Path traversal in n/a (high 7.5)
- [CVE-2024-24323](https://insights.sbomify.com/CVE-2024-24323/): SQL injection in n/a (high 7.2)
- [CVE-2024-46382](https://insights.sbomify.com/CVE-2024-46382/): SQL injection in n/a (medium 6.5)
- [CVE-2025-8974](https://insights.sbomify.com/CVE-2025-8974/): linlinjava litemall JSON Web Token JwtHelper.java hard-coded credentials (medium 6.3)
- [CVE-2025-10291](https://insights.sbomify.com/CVE-2025-10291/): linlinjava litemall cancel WxAftersaleController improper authorization (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6702 is a medium-severity missing authorization vulnerability in linlinjava litemall, published on 26 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6702 exists.

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

## Sources

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

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