# CVE-2024-8043: Vikinghammer Tweet <= 0.2.4 - Stored XSS via CSRF

> Attackers can inject stored XSS payloads via CSRF, allowing admin account takeover in the Vikinghammer Tweet WordPress plugin.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Sep 2024
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-xwc4-p3cg-mmq4

## What is CVE-2024-8043?

CVE-2024-8043 is a medium-severity cross-site scripting vulnerability in Unknown Vikinghammer Tweet, published on 17 Sep 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Vikinghammer Tweet WordPress plugin through 0.2.4 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-2024-8043?

It affects 1 product.


Products: Seanschulte Vikinghammer Tweet.

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

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

## Is CVE-2024-8043 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8043 is a medium-severity cross-site scripting vulnerability in Unknown Vikinghammer Tweet, published on 17 Sep 2024. An attacker needs administrator access to exploit it, 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-2024-8043 exists.

Affected product: Unknown Vikinghammer Tweet. 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-8043/ (Markdown: https://insights.sbomify.com/CVE-2024-8043/index.md)
```

## Sources

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

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