# CVE-2023-6499: lasTunes <= 3.6.1 - Settings Update via CSRF

> Attackers can trick logged-in admins into updating settings via CSRF, potentially injecting stored XSS payloads in the lasTunes WordPress plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Feb 2024
- **Updated:** 6 May 2025
- **Also known as:** GHSA-7h2m-qmmh-q9ff

## What is CVE-2023-6499?

CVE-2023-6499 is a medium-severity vulnerability in Unknown lasTunes, published on 12 Feb 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The lasTunes WordPress plugin through 3.6.1 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack

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

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

It affects 1 product.


Products: Calenfretts Lastunes.

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

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

## Is CVE-2023-6499 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6499 is a medium-severity vulnerability in Unknown lasTunes, published on 12 Feb 2024. Any signed-in user can exploit it over the network, 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-2023-6499 exists.

Affected product: Unknown lasTunes. 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-6499/ (Markdown: https://insights.sbomify.com/CVE-2023-6499/index.md)
```

## Sources

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

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