# CVE-2026-25428: WordPress TS Poll plugin <= 2.5.5 - Server Side Request Forgery (SSRF) vulnerability

> An attacker can exploit a Server-Side Request Forgery vulnerability in the TS Poll WordPress plugin to make arbitrary requests from the server.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-h95f-qq66-v95j

## What is CVE-2026-25428?

CVE-2026-25428 is a medium-severity server-side request forgery vulnerability in totalsoft TS Poll, published on 19 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Server-Side Request Forgery (SSRF) vulnerability in totalsoft TS Poll poll-wp allows Server Side Request Forgery.This issue affects TS Poll: from n/a through <= 2.5.5.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-25428?


## How do I fix CVE-2026-25428?

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

## Is CVE-2026-25428 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25428 and fix it if it is affected.

What it is: CVE-2026-25428 is a medium-severity server-side request forgery vulnerability in totalsoft TS Poll, published on 19 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25428 in the wild and no public exploit code.

Affected product: totalsoft TS Poll. 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-2026-25428/ (Markdown: https://insights.sbomify.com/CVE-2026-25428/index.md)
```

## Sources

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

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