# CVE-2026-38934: Cross-site request forgery in n/a

> A remote attacker can exploit a CSRF vulnerability in Diskover Community to escalate privileges and access sensitive information via the settings process endpoint.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-vccg-rj4f-2wwp

## What is CVE-2026-38934?

CVE-2026-38934 is a high-severity vulnerability in n/a, published on 27 Apr 2026. 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

Cross Site Request Forgery vulnerability in diskoverdata diskover-community v.2.3.5. and before allows a remote attacker to escalate privileges and obtain sensitive information via the public/settings_process.php

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

## Which versions are affected by CVE-2026-38934?


## How do I fix CVE-2026-38934?

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

## Is CVE-2026-38934 being exploited?

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

Public exploit code:

- Multiple CVEs (CVE-2026-38934, CVE-2026-38935, CVE-2026-38936) discovered in diskover-community including CSRF and XSS vulnerabilities with proof-of-concept and impact analysis. (github_poc): https://github.com/VadlaReddySai/cve-writeups

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-38934 and fix it if it is affected.

What it is: CVE-2026-38934 is a high-severity vulnerability in n/a, published on 27 Apr 2026. 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-2026-38934 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-2026-38934/ (Markdown: https://insights.sbomify.com/CVE-2026-38934/index.md)
```

## Sources

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

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