# CVE-2025-3979: dazhouda lecms Password Change index.php cross-site request forgery

> Attackers can force authenticated users to change their passwords via CSRF, potentially leading to account takeover in LECMS.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Apr 2025
- **Updated:** 28 Apr 2025
- **Also known as:** GHSA-x8fg-f2rv-m233

## What is CVE-2025-3979?

CVE-2025-3979 is a medium-severity vulnerability in dazhouda lecms, published on 27 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability classified as problematic has been found in dazhouda lecms 3.0.3. This affects an unknown part of the file /index.php?my-password-ajax-1 of the component Password Change Handler. The manipulation leads to cross-site request forgery. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Lecms Lecms.

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

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

## Is CVE-2025-3979 being exploited?

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

## Other vulnerabilities in dazhouda lecms

- [CVE-2025-3978](https://insights.sbomify.com/CVE-2025-3978/): dazhouda lecms user_set.htm information disclosure (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3979 is a medium-severity vulnerability in dazhouda lecms, published on 27 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3979 exists.

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

## Sources

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

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