LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 4.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25428 is a server-side request forgery issue in the WordPress TS Poll plugin through version 2.5.5. An attacker with high privileges may be able to make the website server send unintended requests. Business risk is moderate because exploitation requires privileged access and has limited confidentiality and integrity impact in the CVSS record.

Executive priority

Treat as a moderate-priority WordPress plugin issue. Address during normal vulnerability management cycles, faster for high-value sites or environments where WordPress servers can reach sensitive internal services.

Technical view

The vulnerability is CWE-918 SSRF in totalsoft TS Poll, package poll-wp, affecting versions through 2.5.5. CVSS 3.1 is 4.4: network attack vector, high attack complexity, high privileges required, no user interaction, scope changed, low confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure is limited to WordPress sites running TS Poll plugin version 2.5.5 or earlier. The CVE data lists default status as unaffected except the stated affected range, so confirm installed plugin identity and version before prioritizing.

Exploitation context

No CISA KEV listing or source-bundle evidence indicates active exploitation. The CVSS vector suggests exploitation requires an authenticated high-privilege context and is not a broad unauthenticated internet-facing risk based on available sources.

Researcher notes

Available public data is sparse. The record identifies SSRF and affected versions but does not include a fixed version, vulnerable endpoint, proof of concept, or confirmed exploitation. Avoid assuming broader impact without vendor details or direct validation in a controlled environment.

Mitigation direction

  • Inventory WordPress sites for the TS Poll / poll-wp plugin.
  • Identify installations running TS Poll version 2.5.5 or earlier.
  • Check the vendor or Patchstack entry for fixed-version guidance.
  • Restrict plugin administration access to trusted high-privilege users.
  • Remove or disable the plugin where it is unnecessary.

Validation and detection

  • Review WordPress plugin inventory for TS Poll version details.
  • Confirm whether any affected site runs version 2.5.5 or earlier.
  • Check logs for unusual server-initiated requests from WordPress hosts.
  • Verify administrative roles are limited to authorized personnel.
  • Track the CVE and Patchstack page for remediation updates.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25428 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N1.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.4Medium
CVSS 3.1 vector shape for CVE-2026-25428Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
totalsoftTS Pollpoll-wp, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.