# CVE-2025-22628: WordPress Filled In Plugin <= 1.9.2 - CSRF to Stored XSS vulnerability

> Attackers can inject malicious scripts via CSRF, leading to stored XSS and potential account takeover in the Filled In WordPress plugin.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **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:** 27 Mar 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-w9c3-ww8v-w4fv

## What is CVE-2025-22628?

CVE-2025-22628 is a high-severity cross-site scripting vulnerability in FolioVision Filled In, published on 27 Mar 2025. 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

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in FolioVision Filled In filled-in allows Stored XSS.This issue affects Filled In: from n/a through <= 1.9.2.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2025-22628 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22628 is a high-severity cross-site scripting vulnerability in FolioVision Filled In, published on 27 Mar 2025. 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-2025-22628 in the wild and no public exploit code.

Affected product: FolioVision Filled In. 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-22628/ (Markdown: https://insights.sbomify.com/CVE-2025-22628/index.md)
```

## Sources

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

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