# CVE-2025-70040: Information disclosure in n/a

> Attackers can obtain sensitive information from log files in the jimeng-web-mcp library due to improper logging practices.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-v9v4-f5wm-phh4

## What is CVE-2025-70040?

CVE-2025-70040 is a medium-severity vulnerability in n/a, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue pertaining to CWE-532: Insertion of Sensitive Information into Log File was discovered in LupinLin1 jimeng-web-mcp v2.1.2. This allows an attacker to obtain sensitive information.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Lupinlin1 Jimeng Web Mcp Server.

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

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

## Is CVE-2025-70040 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70040 is a medium-severity vulnerability in n/a, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-70040 in the wild and no public exploit code.

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

## Sources

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

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