# CVE-2023-35877: WordPress Extra User Details Plugin <= 0.5 is vulnerable to Cross Site Request Forgery (CSRF)

> Attackers can trick users into performing actions that lead to stored XSS, potentially compromising user accounts and site integrity.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:** 13 Nov 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-xpj7-v9x5-6gh9

## What is CVE-2023-35877?

CVE-2023-35877 is a high-severity vulnerability in Vadym K. Extra User Details, published on 13 Nov 2023. 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 (CSRF) vulnerability in Vadym K. Extra User Details allows Stored XSS.This issue affects Extra User Details: from n/a through 0.5.

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

## Which versions are affected by CVE-2023-35877?

It affects 1 product.


Products: Vadimk Extra User Details.

## How do I fix CVE-2023-35877?

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

## Is CVE-2023-35877 being exploited?

There is no known exploitation of CVE-2023-35877 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-35877 and fix it if it is affected.

What it is: CVE-2023-35877 is a high-severity vulnerability in Vadym K. Extra User Details, published on 13 Nov 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-35877 in the wild and no public exploit code.

Affected product: Vadym K. Extra User Details. 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-2023-35877/ (Markdown: https://insights.sbomify.com/CVE-2023-35877/index.md)
```

## Sources

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

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