# CVE-2024-38344: Cross-site request forgery in WP Tweet Walls

> An attacker can trick logged-in users into performing unintended actions on a WordPress site via a malicious page.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jul 2024
- **Updated:** 6 Dec 2024
- **Also known as:** GHSA-jvmf-76g5-h4gv

## What is CVE-2024-38344?

CVE-2024-38344 is a medium-severity vulnerability in Sola Plugins WP Tweet Walls, published on 4 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A cross-site request forgery vulnerability exists in WP Tweet Walls versions prior to 1.0.4. If this vulnerability is exploited, an attacker allows a user who logs in to the WordPress site where the affected plugin is enabled to access a malicious page. As a result, the user may perform unintended operations on the WordPress site.

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

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


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

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

## Is CVE-2024-38344 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38344 is a medium-severity vulnerability in Sola Plugins WP Tweet Walls, published on 4 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38344 in the wild and no public exploit code.

Affected product: Sola Plugins WP Tweet Walls. 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-38344/ (Markdown: https://insights.sbomify.com/CVE-2024-38344/index.md)
```

## Sources

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

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