# CVE-2024-7161: SeaCMS Password Change cross-site request forgery

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

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-v838-ff2j-q3m3

## What is CVE-2024-7161?

CVE-2024-7161 is a medium-severity vulnerability in Seacms Seacms, published on 28 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability classified as problematic was found in SeaCMS 13.0. Affected by this vulnerability is an unknown functionality of the file /member.php?action=chgpwdsubmit of the component Password Change Handler. The manipulation of the argument newpwd/newpwd2 leads to cross-site request forgery. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-272575.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-7161?

It affects 1 product.


Products: Seacms Seacms.

## How do I fix CVE-2024-7161?

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

## Is CVE-2024-7161 being exploited?

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

## Other vulnerabilities in Seacms Seacms

- [CVE-2025-44073](https://insights.sbomify.com/CVE-2025-44073/): SQL injection in n/a (critical 9.8)
- [CVE-2025-44071](https://insights.sbomify.com/CVE-2025-44071/): Code injection in n/a (critical 9.8)
- [CVE-2025-44072](https://insights.sbomify.com/CVE-2025-44072/): SQL injection in n/a (critical 9.8)
- [CVE-2025-44074](https://insights.sbomify.com/CVE-2025-44074/): SQL injection in n/a (critical 9.8)
- [CVE-2025-29647](https://insights.sbomify.com/CVE-2025-29647/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7161 and fix it if it is affected.

What it is: CVE-2024-7161 is a medium-severity vulnerability in Seacms Seacms, published on 28 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-7161 exists.

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

## Sources

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

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