# CVE-2025-32245: WordPress Featured Posts Scroll plugin <= 1.25 - CSRF to Stored Cross Site Scripting (XSS) vulnerability

> Attackers can exploit CSRF to inject stored XSS payloads, potentially executing malicious scripts in victim browsers.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **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:** 16 May 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-h4wc-pvj9-rqm4

## What is CVE-2025-32245?

CVE-2025-32245 is a high-severity vulnerability in Chaser324 Featured Posts Scroll, published on 16 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-Site Request Forgery (CSRF) vulnerability in Chaser324 Featured Posts Scroll featured-posts-scroll allows Stored XSS.This issue affects Featured Posts Scroll: from n/a through <= 1.25.

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

## Which versions are affected by CVE-2025-32245?


## How do I fix CVE-2025-32245?

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

## Is CVE-2025-32245 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32245 and fix it if it is affected.

What it is: CVE-2025-32245 is a high-severity vulnerability in Chaser324 Featured Posts Scroll, published on 16 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-32245 in the wild and no public exploit code.

Affected product: Chaser324 Featured Posts Scroll. 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-2025-32245/ (Markdown: https://insights.sbomify.com/CVE-2025-32245/index.md)
```

## Sources

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

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