# CVE-2025-28355: Cross-site request forgery in n/a

> Attackers can exploit CSRF in Volmarg Personal Management System to execute arbitrary code and access sensitive information due to insecure cookie settings.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A: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:** 18 Apr 2025
- **Updated:** 18 Apr 2025
- **Also known as:** GHSA-cf79-3x47-jx24

## What is CVE-2025-28355?

CVE-2025-28355 is a medium-severity vulnerability in n/a, published on 18 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

Volmarg Personal Management System 1.4.65 is vulnerable to Cross Site Request Forgery (CSRF) allowing attackers to execute arbitrary code and obtain sensitive information via the SameSite cookie attribute defaults value set to none

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

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

It affects 1 product.


Products: Personal-Management-System Personal Management System.

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

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

## Is CVE-2025-28355 being exploited?

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

Public exploit code:

- It was identified that the https://github.com/Volmarg/personal-management-system application is vulnerable to CSRF attacks. (github_poc): https://github.com/abbisQQ/CVE-2025-28355

## Other vulnerabilities in n/a

- [CVE-2023-43838](https://insights.sbomify.com/CVE-2023-43838/): File upload in n/a (high 7.8)
- [CVE-2025-29453](https://insights.sbomify.com/CVE-2025-29453/): Server-side request forgery in n/a (medium 6.5)
- [CVE-2025-29454](https://insights.sbomify.com/CVE-2025-29454/): Server-side request forgery in n/a (medium 6.5)
- [CVE-2025-29455](https://insights.sbomify.com/CVE-2025-29455/): Server-side request forgery in n/a (medium 6.5)
- [CVE-2025-29456](https://insights.sbomify.com/CVE-2025-29456/): Server-side request forgery in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-28355 is a medium-severity vulnerability in n/a, published on 18 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-28355 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-2025-28355/ (Markdown: https://insights.sbomify.com/CVE-2025-28355/index.md)
```

## Sources

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

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