# CVE-2023-7297: TwitterPosts <= 1.0.2 - Settings Update via CSRF

> Attackers can force logged-in administrators to update TwitterPosts plugin settings via CSRF, potentially altering site configuration.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N`)
- **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:** 15 May 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-7rv8-qgm5-32cr

## What is CVE-2023-7297?

CVE-2023-7297 is a low-severity vulnerability in Unknown TwitterPosts, published on 15 May 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The TwitterPosts WordPress plugin through 1.0.2 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

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

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

It affects 1 product.


Products: Reneade Twitterposts.

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

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

## Is CVE-2023-7297 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-7297 is a low-severity vulnerability in Unknown TwitterPosts, published on 15 May 2025. 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-2023-7297 exists.

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

## Sources

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

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