# CVE-2025-8282: SureForms < 1.9.1 - Admin+ Stored XSS

> Admin users can inject malicious scripts via unsanitized parameters in SureForms, leading to stored XSS attacks.

- **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:** 23 Sep 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-m7f8-rpm5-xmqj

## What is CVE-2025-8282?

CVE-2025-8282 is a low-severity cross-site scripting vulnerability in Unknown SureForms, published on 23 Sep 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The SureForms  WordPress plugin before 1.9.1 does not sanitise and escape some parameters when outputing them in the page, which could allow admin and above users to perform Cross-Site Scripting attacks.

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


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

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

## Is CVE-2025-8282 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8282 is a low-severity cross-site scripting vulnerability in Unknown SureForms, published on 23 Sep 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-2025-8282 exists.

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

## Sources

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

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