# CVE-2024-31086: WordPress Change default login logo,url and title plugin <= 2.0 - CSRF to XSS vulnerability

> A CSRF vulnerability in a WordPress plugin allows attackers to inject malicious scripts, potentially leading to code execution or security bypass.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **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:** 15 Apr 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-9767-v9q2-46c6

## What is CVE-2024-31086?

CVE-2024-31086 is a high-severity cross-site scripting vulnerability in Venugopal Change default login logo,url and title, published on 15 Apr 2024. 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 Venugopal Change default login logo,url and title allows Cross-Site Scripting (XSS).This issue affects Change default login logo,url and title: from n/a through 2.0.

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

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


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

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

## Is CVE-2024-31086 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-31086 is a high-severity cross-site scripting vulnerability in Venugopal Change default login logo,url and title, published on 15 Apr 2024. 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-2024-31086 in the wild and no public exploit code.

Affected product: Venugopal Change default login logo,url and title. 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-31086/ (Markdown: https://insights.sbomify.com/CVE-2024-31086/index.md)
```

## Sources

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

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