# CVE-2024-48341: Cross-site request forgery in n/a

> An attacker can trick authenticated administrators into performing unauthorized actions, such as adding shops, via a Cross-Site Request Forgery vulnerability.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/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:** 8 Sep 2025
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-76gq-jjh6-68rh

## What is CVE-2024-48341?

CVE-2024-48341 is a low-severity vulnerability in n/a, published on 8 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

dingfanzu CMS V1.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/doAdminAction.php?act=addShop

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

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

It affects 1 product.


Products: Geeeeeeeek Dingfanzu.

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

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

## Is CVE-2024-48341 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-28100](https://insights.sbomify.com/CVE-2025-28100/): SQL injection in n/a (critical 9.8)
- [CVE-2024-8302](https://insights.sbomify.com/CVE-2024-8302/): dingfanzu CMS chpwd.php sql injection (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48341 is a low-severity vulnerability in n/a, published on 8 Sep 2025. 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-48341 exists.

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

## Sources

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

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