# CVE-2024-25932: WordPress Change Table Prefix plugin <= 2.0 - Cross Site Request Forgery (CSRF) vulnerability

> A Cross-Site Request Forgery vulnerability in the Change Table Prefix WordPress plugin allows attackers to perform unauthorized actions on behalf of authenticated users.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **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:** 28 Feb 2024
- **Updated:** 11 May 2026
- **Also known as:** GHSA-j4j6-xqv7-cqrg

## What is CVE-2024-25932?

CVE-2024-25932 is a medium-severity vulnerability in Manish Kumar Agarwal Change Table Prefix, published on 28 Feb 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 Manish Kumar Agarwal Change Table Prefix change-table-prefix allows Cross Site Request Forgery.This issue affects Change Table Prefix: from n/a through <= 2.0.

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

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

It affects 1 product.


Products: Youngtechleads Change Table Prefix.

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

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

## Is CVE-2024-25932 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25932 is a medium-severity vulnerability in Manish Kumar Agarwal Change Table Prefix, published on 28 Feb 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-25932 in the wild and no public exploit code.

Affected product: Manish Kumar Agarwal Change Table Prefix. 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-25932/ (Markdown: https://insights.sbomify.com/CVE-2024-25932/index.md)
```

## Sources

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

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